Remote MCP phone calls for ChatGPT and AI agents
Connect ChatGPT first, or use any compatible AI host that supports remote Streamable HTTP MCP and OAuth. ClawCall exposes eleven bounded tools for real, user-directed English-language calls to US +1 numbers, then returns lifecycle and network outcome plus captured transcript evidence when present.
https://api.clawcall.dev/mcpChoose your current agent guide
Setup belongs to the host—not only the model inside it. ChatGPT and Claude are live UI verified; the other pages distinguish first-party documentation review, host restrictions, and fallback-only paths.
ChatGPT
Connect ChatGPT to ClawCall remote MCP with OAuth, PKCE S256, eleven tools, safe verification, and transcript-backed US phone calls.
Connect ChatGPT →Official docs reviewed · 2026-08-23Google Gemini
Connect Google Gemini to ClawCall with current MCP steps, Always allow guidance, safe verification, troubleshooting, and cited sources.
Open guide →Live UI verified · 2026-08-23Claude
Connect Claude to ClawCall with current MCP steps, Always allow guidance, safe verification, troubleshooting, and cited sources.
Open guide →Official docs reviewed · 2026-08-23Microsoft Copilot
Connect Microsoft Copilot to ClawCall with current MCP steps, Always allow guidance, safe verification, troubleshooting, and cited sources.
Open guide →Official docs reviewed · 2026-08-23Perplexity
Connect Perplexity to ClawCall with current MCP steps, Always allow guidance, safe verification, troubleshooting, and cited sources.
Open guide →Official docs reviewed · 2026-08-23OpenAI Codex
Connect OpenAI Codex to ClawCall with current MCP steps, Always allow guidance, safe verification, troubleshooting, and cited sources.
Open guide →Official docs reviewed · 2026-08-23Cursor
Connect Cursor to ClawCall with current MCP steps, Always allow guidance, safe verification, troubleshooting, and cited sources.
Open guide →Official docs reviewed · 2026-08-23Grok Build
Connect Grok Build to ClawCall with current MCP steps, Always allow guidance, safe verification, troubleshooting, and cited sources.
Open guide →Official docs reviewed · 2026-08-23Meta AI
Check Meta AI and ClawCall compatibility, then use a supported agent host or server-side REST fallback with safe, cited steps.
Open guide →Official docs reviewed · 2026-08-23DeepSeek
Check DeepSeek and ClawCall compatibility, then use a supported agent host or server-side REST fallback with safe, cited steps.
Open guide →The host must support the connection contract
ClawCall works with AI hosts that support remote Streamable HTTP MCP and OAuth. Host features can vary by plan, workspace policy, admin settings, and version. Grok Build is listed separately from consumer Grok, and Meta AI / DeepSeek are labeled fallback-only rather than being given invented connector support.
A bounded workflow, not a raw API dump
get_calling_guide is required before any ClawCall work. Before each call, the host reads current outbound guidance; after a call, it polls status and reads the transcript evidence actually captured. A network outcomedoes not prove the user's task succeeded—captured evidence does.
get_calling_guideReadRequired before any ClawCall work. Read current workflow guidance and examples before placing calls.
get_balanceReadRead the signed-in account's plan and remaining trial allowance.
get_call_settingsReadRead reusable voice/personality, reserved-number capabilities, and inbound-assistant availability.
update_call_settingsWriteUpdate global or inbound call settings in separate calls.
place_callWriteStart one real outbound phone call and return immediately.
place_call_and_waitWriteStart one call and wait up to 90 seconds for an initial result.
get_callReadRead a call's lifecycle, outcome, and a nullable bounded transcript tail.
get_call_transcriptReadRead the transcript evidence captured for a call.
list_callsReadRead recent call history for the connected account.
get_recordingReadGet a temporary, playable recording URL when one is available.
hangup_callWriteStop a queued or live phone call.
Your API key stays out of the AI host
Remote MCP uses OAuth 2.1 authorization code with PKCE S256 and Dynamic Client Registration. The host discovers ClawCall's authorization-server and protected-resource metadata, then receives revocable tokens mapped to one signed-in account. Review the exact destination and permissions on the consent screen.
calls:readRead plan/trial state, call settings, reserved-number status, call status, captured transcript evidence when present, history, and temporary recording access when available.
calls:writePlace and hang up real phone calls or update call settings when you ask the assistant to do so.
Generic remote MCP setup
- Confirm the host supports remote Streamable HTTP MCP, OAuth, PKCE S256, and Dynamic Client Registration. ClawCall serves MCP revision
2026-07-28with legacy negotiation for 2025-era clients. - Add
https://api.clawcall.dev/mcpas a remote server. Do not paste a ClawCall API key. - Sign in to ClawCall and approve
calls:readandcalls:write. - Verify safely: “Check my ClawCall plan and remaining trial allowance. Do not place a call.”
- Review all eleven tools, then use a normal request. The enabled host can select ClawCall automatically.
Choose the connection method your host supports
Hosted MCP — preferred
For compatible AI hosts. One endpoint, ClawCall OAuth, bounded tools, and automatic tool selection.
Read setup →REST API
For custom runtimes and direct HTTP integrations. REST clients use API keys or the documented trial flow.
Read setup →Packaged agent skill
For skill-aware agents that need ClawCall's calling procedure and REST workflow.
Read setup →Hosted MCP FAQs
Which AI products can connect to ClawCall?
ClawCall works directly with AI hosts that support remote Streamable HTTP MCP and OAuth. The ten-agent catalog distinguishes direct, host-restricted, and fallback-only paths; only ChatGPT and Claude are labeled live UI verified for this release.
Does an MCP host receive my ClawCall API key?
No. The host receives revocable OAuth tokens for the scopes you approve. ClawCall API keys are for REST clients and are not copied into the AI host.
Do I need to choose ClawCall for every request?
Usually not. Once the connection is enabled, a compatible host can select ClawCall automatically from a normal phone-call request. A host's tool picker is useful for checking or forcing the connection, but it is optional.
How do I disconnect an AI host?
Remove ClawCall in the AI host, then open ClawCall Dashboard → Settings → Connected AI assistants and select Disconnect. Disconnecting in ClawCall revokes the connection's token family.