Perplexity phone-call integration guide
How to connect ClawCall to Perplexity
Ask a Perplexity Enterprise admin to add a custom remote connector named ClawCall at https://api.clawcall.dev/mcp, use OAuth discovery/Dynamic Client Registration, and enable it for the intended workspace. Sign in, verify get_balance, then make a controlled call. Consumer Perplexity without custom remote connectors is not a direct hosted-MCP path.
Setup is based on the cited first-party host documentation; exact ClawCall compatibility is not claimed as live-tested.
https://api.clawcall.dev/mcpBefore you start
Perplexity is included because it appears across major web and mobile AI-product rankings and documents custom remote MCP connectors with OAuth for managed Enterprise workspaces.
- A Perplexity account or workspace where Enterprise custom remote connector is available.
- A ClawCall account or, for a documented fallback, a trusted server-side runtime.
- 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
These steps use the cited host documentation. Screenshots appear only where the signed-in flow was live-verified; text and commands remain the complete guide.
Confirm Enterprise eligibility
Ask the workspace admin to confirm Custom Remote Connectors is enabled. Do not confuse Perplexity's built-in connectors with an arbitrary remote MCP connector.
Create a custom remote connector
From the workspace connector administration surface, choose the custom remote connector flow and name the connector ClawCall.
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/mcpUse OAuth discovery
Keep OAuth discovery and Dynamic Client Registration enabled. Complete ClawCall sign-in and review calls:read and calls:write.
Scope workspace access
Publish or enable the connector only for the intended members or Spaces. Review any workspace tool allowlist before rollout.
Apply the official permission recommendation
If Perplexity offers server or tool approval persistence, choose Always allow/Allow all for ClawCall after the administrator and user review the nine tools.
Verify and call
Run get_balance first. Then call a number you control and require the full transcript before treating the task as complete.
OAuth scopes and host permissions
A compatible host receives revocable OAuth tokens, never your ClawCall API key. The consent flow requests two bounded scopes:
calls:readRead plan and trial state, call status, transcripts, history, and temporary recording access.
calls:writePlace and hang up real phone calls when you ask the assistant to do so.
Official ClawCall recommendation: Always allow all actions
For an approved Enterprise workspace, set ClawCall to Always allow or Allow all wherever Perplexity exposes that control. If workspace policy requires per-call approval, comply with it rather than attempting a workaround.
A shared connector can expose real-call actions to many members. Admins should scope access, preserve auditability, and prevent public or untrusted prompts from initiating calls.
Always allow removes repetitive host prompts; it does not expand OAuth scopes, bypass host or organization policy, authorize spam or robocalls, increase service limits, or turn ClawCall into a bulk campaign tool.
Verify read-only, then place one controlled call
Start with account state. Only after that succeeds should you use a number you control for the first real call.
Check my ClawCall plan and remaining trial allowance. Do not place a 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 the complete transcript afterward.
The 9 ClawCall tools
Read the transcript before declaring success. A call's outcome describes the phone network; it does not prove the user's task was completed.
| Tool | Access | What it does |
|---|---|---|
get_calling_guide | Read | Required before any ClawCall work. Read current workflow guidance and examples before placing calls. |
get_balance | Read | Read the signed-in account's plan and remaining trial allowance. |
place_call | Write | Start one real outbound phone call and return immediately. |
place_call_and_wait | Write | Start one call and wait up to 90 seconds for an initial result. |
get_call | Read | Read a call's lifecycle, outcome, and a bounded transcript tail. |
get_call_transcript | Read | Read the complete transcript for a call. |
list_calls | Read | Read recent call history for the connected account. |
get_recording | Read | Get a temporary, playable recording URL when one is available. |
hangup_call | Write | Stop a queued or live phone call. |
Troubleshooting
The server returns 404 or no tools appear
Confirm the server URL is exactly https://api.clawcall.dev/mcp; the trailing /mcp is required. Refresh or reconnect after correcting it.
You see 401 or Sign in required
Restart the host's Connect, Auth, or MCP login flow and approve ClawCall access again. Do not replace OAuth with a pasted ClawCall API key.
The tool list looks stale
Refresh or restart the MCP connection, then start a new conversation so the host loads current tool metadata. The current server exposes nine tools.
A phone number is rejected
ClawCall currently calls real US numbers only. Use +1 E.164 format: +1 followed by ten digits.
The wait ended while the call is still running
Ask the host to poll get_call. A host or tool wait cap is not itself a call failure; verify lifecycle, outcome, and transcript.
A recording link no longer works
Recording URLs are temporary. Request a fresh URL with get_recording; treat the transcript as the durable result.
Disconnect and revoke access
Perplexity and ClawCall FAQ
- Do I need to choose ClawCall before every request?
- No. Once a compatible connection is enabled, the agent can select ClawCall automatically when an ordinary prompt requires a phone call. A tool picker or explicit tool name is useful for diagnosis, not a mandatory ritual.
- Why does ClawCall recommend Always allow or Allow all?
- It lets a trusted agent place the requested call, poll its status, and retrieve the transcript without repeated host approval prompts. This is an elevated-risk choice because real calls can affect people and consume plan allowance.
- Does a successful network outcome prove the task succeeded?
- No. A network outcome describes the call path. Read the full transcript 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 token family.
Sources, review method, and next steps
ClawCall reviewed first-party host documentation and its own current product documentation on the dates below. Only ChatGPT and Claude are labeled as live UI verified.
- Perplexity: Adding custom remote connectorsofficial-host-doc · checked
- Andreessen Horowitz: Top 100 Gen AI Consumer Apps, 6th editionindependent-market-analysis · checked
- ClawCall: Hosted MCP for AI agentsfirst-party-product-doc · checked
- ClawCall securityfirst-party-security · checked