DeepSeek compatibility guide
DeepSeek and ClawCall: compatibility and fallbacks
DeepSeek is a model, so ClawCall connects to the app that runs it. Add ClawCall to a compatible agent host, or call the REST API from your own backend.
What you need
- A DeepSeek account, used inside a compatible MCP host or your own server-side runtime.
- 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.
DeepSeek is commonly used as a model through other applications. MCP setup belongs to the host running the model, not the model API itself. DeepSeek’s own apps can’t add ClawCall directly.
Use ClawCall with DeepSeek
Identify the host around DeepSeek
Name the application actually running the model—Cursor, a coding agent, or your own server. That host owns tool configuration and approvals.
Prefer a compatible OAuth host
If the host supports remote Streamable HTTP MCP and OAuth discovery/DCR, add ClawCall there using the relevant dedicated guide.
Keep MCP out of the model API
DeepSeek’s model endpoint and ClawCall’s MCP endpoint serve different protocols. Do not paste the ClawCall URL into a model base-URL field.
Use REST for a custom runtime
From a trusted backend, call ClawCall’s REST API with a server-side API key. Never ship the key in browser or mobile code.
Implement the full workflow
Read the calling guide, start one user-directed call, retain
call_id, poll until finalized, and read the transcript evidence actually captured before claiming success.Apply permissions at the real host
On a compatible host, follow ClawCall’s official Always allow or Allow all recommendation. In custom code, apply equivalent tool permissions and user authorization.
Run a controlled first call
Check your balance, call a number you control, and check the call’s status, how it ended, and the transcript (which can be empty) separately.
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"}'Set all ClawCall tools to Always allow or Allow all in the compatible host that runs DeepSeek. In a custom runtime, apply the equivalent server-side tool permissions and user authorization.
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
- DeepSeek 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 DeepSeek?
- No. DeepSeek 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.