Meta AI compatibility guide
Meta AI and ClawCall: compatibility and fallbacks
Consumer Meta AI can’t add tools like ClawCall. Use a compatible agent host with ClawCall, or call the REST API from your own backend.
What you need
- A Meta AI account, plus either a compatible MCP host or a trusted server-side runtime for the REST fallback.
- A ClawCall account, plus an API key if you use the REST fallback.
- 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.
Consumer Meta AI can’t add outside tools like ClawCall, and the Muse app has no ClawCall connector. Meta says Muse can build custom connectors from a service’s API information, and that Muse Code connects remote MCP servers with an OAuth sign-in; we haven’t tested ClawCall in either. Never paste a ClawCall API key into Meta AI.
Use ClawCall with Meta AI
Identify the actual Meta surface
Consumer Meta AI and Muse Code are different products. The consumer assistant does not publish the arbitrary MCP setup required by ClawCall.
Keep your API key out of Meta AI
Never paste a ClawCall API key into a prompt, a public bot, or a custom header. ClawCall connects through a sign-in, not a pasted key.
Choose a supported host
For OAuth and automatic tool selection, use one of the directly supported guides such as ChatGPT, Claude, Codex, Cursor, or Grok Build.
Or choose a trusted REST runtime
If your Meta model is embedded in your own application, follow ClawCall REST documentation from the server-side runtime. Store the API key in an environment secret, never client-side.
Load the calling procedure
Use the ClawCall skill, or follow the same steps yourself: start one call, save the
call_id, check its status until it ends, and read the transcript evidence when present.Verify before calling
Check balance first. Then use a number you control and a narrowly bounded task.
Check back for a direct path
If Meta documents Streamable HTTP with OAuth discovery for the surface you use, you can switch to the hosted MCP endpoint.
Call from your own server
These commands run on a server you control, never in a chat or a web page. Keep the API key in a secret.
curl https://api.clawcall.dev/balance \
-H 'X-Api-Key: clawcall_sk_...'curl -X POST https://api.clawcall.dev/call \
-H 'Content-Type: application/json' \
-H 'X-Api-Key: clawcall_sk_...' \
-d '{"to":"+1XXXXXXXXXX","task":"Call my phone and say this is a controlled test"}'When you use a compatible host, set all ClawCall tools to Always allow or Allow all for the complete workflow. A custom REST runtime has no host approval toggle and uses server-side authorization instead.
Allow all or Always allow applies in the compatible MCP host that owns tool permissions. A server-side REST runtime uses its own authorization controls instead of a host approval toggle.
Troubleshooting
- The consumer app has no custom MCP setting
- Meta AI can’t connect ClawCall directly. Use an app from the guides list, or call the API from your own server.
- The REST request returns 401
- Keep the ClawCall API key in the server environment and send it in
X-Api-Key. Never paste it into a consumer prompt or ship it in browser code. - The REST request returns an invalid phone error
- Use a real US number in +1 E.164 format: +1 followed by ten digits.
- The call is still running
- Save
call_idand pollGET /call/:iduntil lifecycle is finalized. A client timeout is not itself a call failure. - The model claims success too early
- Require the runtime to retrieve and read the transcript evidence actually captured before reporting that the real-world task succeeded.
Turn it off
- If you connected ClawCall to another app, remove it there, then disconnect it in your ClawCall dashboard under Settings → Connected AI assistants.
- If you call from your own server, revoke or replace the API key.
Questions
- Can I connect ClawCall directly to Meta AI?
- No. Meta AI can’t add ClawCall on its own today. Use an app that connects ClawCall, or call the API from your own server.
- Where do I allow ClawCall to call without asking?
- In the app you connect ClawCall to. If you call the API from your own server, your server decides what it’s allowed to do.
- How do I know the call worked?
- Read what was actually said in the transcript. A call that connected doesn’t mean the task got done.
- How do I turn it off?
- Disconnect ClawCall in the app you connected it to, or revoke the API key your server uses.
- 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
Make calls from an app that connects
Connect ClawCall to an app that supports it, or call the API from your own server.