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

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.

Based on DeepSeek’s documentation; no direct connection to testUpdated

Choose a compatible hostRead the REST docs
Direct connector
None documented
Supported paths
A compatible MCP host, or the REST API
Authentication
Host OAuth, or a server-side API key

Before you start

Availability. DeepSeek is commonly used as a model through other applications. MCP setup belongs to the host running the model, not the model API itself. The reviewed DeepSeek documentation does not provide a first-party ClawCall-compatible hosted-MCP client.
  • 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.

Use ClawCall safely with DeepSeek

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. Run a controlled first call

    Check balance, call a number you control, and verify lifecycle, outcome, and the nullable transcript field separately.

Authentication and tool permissions

OAuth belongs to the compatible host. A custom REST runtime uses a server-side ClawCall API key instead. Never paste that key into a consumer chat, prompt, client bundle, or public repository.

Recommended in a compatible host: Always allow

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.

Server-side REST fallback

These commands run in a trusted backend, not in a consumer prompt, browser bundle, or model base-URL field. Keep the API key in an environment secret.

1. Verify the key and balance
curl https://api.clawcall.dev/balance \
  -H 'X-Api-Key: clawcall_sk_...'
2. Start one controlled call
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"}'
Automatic selection needs a host. The model can pick ClawCall on its own only when it runs inside a compatible MCP host with ClawCall connected.

What the fallback runtime must implement

  1. Authenticate the user and keep the ClawCall key server-side.
  2. Start one explicit, user-directed call and keep the returned call_id.
  3. Poll GET /call/:id until lifecycle is finalized.
  4. Read the transcript evidence actually captured before reporting task success.
Open the REST API documentationChoose a compatible OAuth host instead

Troubleshooting

The consumer app has no custom MCP setting
That is expected for this fallback-only path. Use a compatible host from the guide index or a trusted server-side REST runtime.
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_id and poll GET /call/:id until 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.

Disconnect and revoke access

  1. If you used a separate compatible MCP host, remove ClawCall there and revoke its connection in ClawCall Dashboard → Settings → Connected AI assistants.
  2. If you used the REST fallback, rotate or revoke the server-side API key and disable the backend tool route. There is no direct DeepSeek connection to remove.

FAQ

Can I connect ClawCall directly to DeepSeek?
Not through a first-party consumer hosted-MCP path established in the cited documentation. Use a compatible host or a trusted server-side REST runtime.
Where does ClawCall’s Always allow recommendation apply?
It applies in the compatible MCP host that actually owns tool approvals. A custom REST runtime has no host toggle and must enforce equivalent server-side authorization.
Does a successful network outcome prove the task succeeded?
No. Poll the call, then read the transcript evidence actually captured before claiming the real-world task was completed.
How do I revoke fallback access?
Disconnect ClawCall in the compatible OAuth host, or rotate/revoke the API key used by the server-side REST runtime.
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 DeepSeek’s own documentation and ClawCall’s product documentation, checked on the dates below.

  1. DeepSeek API documentationOfficial 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

Can DeepSeek make phone calls?Meta AI setup guideGoogle Gemini setup guideHow to give your AI agent a phone numberAll 12 setup guidesFor AI agentsAI phone call APIAI phone calls with ClawCallAPI docsSecurity

Place calls from a supported path

Connect ClawCall to a compatible OAuth host, or call the REST API from a trusted backend.

Start freeAll setup guides
Text ClawCall