First month free with promo codeFirst month free with codeEveryone else starts with 30 free calls and 30 minutes.Redeem DEEPGRAMStart free

Perplexity setup guide

Connect Perplexity to ClawCall with remote MCP

A Perplexity Enterprise admin adds ClawCall as a custom remote connector, and members sign in with OAuth. Consumer Perplexity accounts do not have custom remote connectors.

Based on Perplexity’s documentation; not yet tested live with ClawCallUpdated

Remote MCP endpointhttps://api.clawcall.dev/mcp
Setup surface
Enterprise custom remote connector
Transport
Streamable HTTP
Authentication
OAuth discovery and DCR

Before you start

Availability. Custom remote connectors are an Enterprise workspace feature controlled by administrators and policy. A consumer Perplexity account without that control cannot follow this guide. Availability, publication, and tool permissions can vary by workspace.
  • A Perplexity Enterprise workspace with custom remote connectors turned on.
  • A ClawCall account.
  • A real US destination in +1 E.164 format for any call you choose to place.
  • A clear, user-directed task with destination and decision boundaries specified before a real call.

Connect Perplexity to ClawCall

  1. Confirm Enterprise eligibility

    Ask the workspace admin to confirm Custom Remote Connectors is turned on. Perplexity’s built-in connectors are a different feature.

  2. Create a custom remote connector

    From the workspace connector administration surface, choose the custom remote connector flow and name the connector ClawCall.

  3. Add the MCP endpoint

    Use https://api.clawcall.dev/mcp as the Streamable HTTP server URL. Do not paste a ClawCall API key into connector settings.

    https://api.clawcall.dev/mcp
  4. Use OAuth discovery

    Keep OAuth discovery and Dynamic Client Registration enabled. Complete ClawCall sign-in and review calls:read and calls:write.

  5. Scope workspace access

    Publish or enable the connector only for the intended members or Spaces. Review any workspace tool allowlist before rollout.

  6. Always allow ClawCall

    If Perplexity offers saved approvals for a server or tool, choose Always allow for ClawCall once the admin has reviewed the eleven tools.

OAuth scopes and host permissions

Perplexity signs in with OAuth and asks for two scopes: calls:read to read account and call state, and calls:write to place or hang up calls and change call settings. It gets revocable tokens, never your ClawCall API key.

Recommended: Always allow ClawCall

In an approved Enterprise workspace, set ClawCall to Always allow wherever Perplexity offers that control, so the complete calling workflow runs without repeated prompts.

Always allow only skips the repeated approval prompts. It does not widen the two OAuth scopes, override workspace policy, or allow bulk or automated calling.

Verify read-only, then place one controlled call

Check account state first. Only after that succeeds, place the first real call to a number you control.

1. Read-only check

Check my ClawCall plan and remaining trial allowance. Do not place a call.

2. One controlled call

Using ClawCall, call my phone at +1XXXXXXXXXX. Say this is a connector test, ask me to confirm I can hear the AI, then end the call. Show me any transcript evidence actually captured afterward.

Ask normally. Perplexity can pick ClawCall automatically when a task needs a phone call; choosing the connector by hand is optional.

Tools and troubleshooting

ClawCall gives Perplexity 11 tools: read tools for the calling guide, your plan, settings, calls, transcripts, and recordings, and write tools that place, wait on, or hang up a call and update settings. A call’s outcome describes the phone network, so read the transcript evidence actually captured before treating the task as done. The remote MCP reference lists every tool and scope.

If no tools appear, check that the server URL ends in /mcp. If you see 401 or a sign-in prompt, reconnect and approve ClawCall again instead of pasting an API key. For anything else, see troubleshooting in the docs.

Disconnect and revoke access

  1. Disconnect or remove ClawCall in Perplexity.
  2. Open ClawCall Dashboard → Settings → Connected AI assistants → Disconnect to revoke its OAuth tokens.

FAQ

Do I need to choose ClawCall before every request?
No. Once the connection is enabled, the agent can pick ClawCall automatically when an ordinary request needs a phone call. Naming the tool is optional and mainly useful for troubleshooting.
What does it cost?
The ClawCall trial includes 30 calls and 30 minutes, whichever lasts later. After that, a paid plan covers ongoing calls. The host itself may need its own plan for plugins or connectors.
Does a successful network outcome prove the task succeeded?
No. A network outcome describes the call path. Read the transcript evidence actually captured before claiming a reservation, cancellation, price, or other real-world task was completed.
How do I revoke access?
Remove or disconnect ClawCall in the host, then open ClawCall Dashboard → Settings → Connected AI assistants → Disconnect to revoke that connection’s tokens.
How long does ClawCall keep transcripts and recordings?
ClawCall deletes transcripts 7 days after a call ends and recordings 10 minutes after a call ends. Recording URLs are temporary and cannot be renewed after they expire.

Sources

Setup steps come from Perplexity’s own documentation and ClawCall’s product documentation, checked on the dates below.

  1. Perplexity: Adding custom remote connectorsOfficial host documentation · checked
  2. Andreessen Horowitz: Top 100 Gen AI Consumer Apps, 6th editionIndependent market analysis · checked
  3. ClawCall: Hosted MCP for AI agentsClawCall documentation · checked
  4. ClawCall securityClawCall security · checked

Related pages

Give Perplexity a phone line

Create a ClawCall account, add the endpoint, and start with the read-only check. The trial includes 30 calls and 30 minutes, whichever lasts later.

Text ClawCall