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

Cursor setup guide

Connect Cursor to ClawCall with remote MCP

Add ClawCall as a custom MCP server in Cursor, or add a clawcall entry to mcp.json, then sign in when Cursor opens OAuth. Cursor uses the tools automatically when a task needs a call.

Based on Cursor’s documentation; not yet tested live with ClawCallUpdated

Remote MCP endpointhttps://api.clawcall.dev/mcp
Start freeSign in
Setup surface
Customize / mcp.json
Transport
Streamable HTTP
Authentication
OAuth with DCR

Before you start

Availability. Personal, workspace, and team-admin configuration paths differ. A team allowlist or network policy can block remote URLs. ClawCall supports DCR, so static OAuth credentials are not needed.
  • Cursor, with access to its MCP settings (Customize or mcp.json).
  • A ClawCall account.
  • 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 Cursor to ClawCall

  1. Open Cursor MCP settings

    Open Customize and the MCP server section. Choose the custom-server path rather than installing an unrelated marketplace entry.

  2. Add the remote URL

    Create a server named clawcall with only the remote URL. No API-key header or static OAuth object is required because ClawCall supports DCR.

    {
  "mcpServers": {
    "clawcall": {
      "url": "https://api.clawcall.dev/mcp"
    }
  }
}

  3. Authenticate

    Enable the server and follow Cursor’s OAuth prompt. Sign in to ClawCall and review calls:read and calls:write.

  4. Review Available Tools

    Confirm all eleven tools appear. Check MCP Logs if the server is disabled, blocked, or returns an authentication error.

  5. Allow every ClawCall tool

    The team allowlist is an admin control. For your own use, leave the ClawCall tool allowlist empty so every tool is allowed, and choose Always allow when Cursor asks to approve a run.

OAuth scopes and host permissions

Cursor signs in with OAuth and asks for two scopes: calls:read to read account and call state, and calls:write to place or hang up calls and change call settings. It gets revocable tokens, never your ClawCall API key.

Recommended: allow all ClawCall tools

Leave the ClawCall tool allowlist empty so every discovered tool is allowed, and choose Always allow for execution approvals. That gives Cursor the complete calling workflow.

Always allow only skips the repeated approval prompts. It does not widen the two OAuth scopes, override team policy, or allow bulk or automated calling.

Verify read-only, then place one controlled call

Check account state first. Only after that succeeds, place the first real call to a number you control.

1. Read-only check

Check my ClawCall plan and remaining trial allowance. Do not place a call.

2. One controlled 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 any transcript evidence actually captured afterward.

Ask normally. Cursor can pick ClawCall automatically when a task needs a phone call; naming the tool is optional.

Tools and troubleshooting

ClawCall gives Cursor 11 tools: read tools for the calling guide, your plan, settings, calls, transcripts, and recordings, and write tools that place, wait on, or hang up a call and update settings. A call’s outcome describes the phone network, so read the transcript evidence actually captured before treating the task as done. The remote MCP reference lists every tool and scope.

If no tools appear, check that the server URL ends in /mcp. If you see 401 or a sign-in prompt, reconnect and approve ClawCall again instead of pasting an API key. For anything else, see troubleshooting in the docs.

Disconnect and revoke access

  1. Disconnect or remove ClawCall in Cursor.
  2. Open ClawCall Dashboard → Settings → Connected AI assistants → Disconnect to revoke its OAuth tokens.

FAQ

Do I need to choose ClawCall before every request?
No. Once the connection is enabled, the agent can pick ClawCall automatically when an ordinary request needs a phone call. Naming the tool is optional and mainly useful for troubleshooting.
What does it cost?
The ClawCall trial includes 30 calls and 30 minutes, whichever lasts later. After that, a paid plan covers ongoing calls. The host itself may need its own plan for plugins or connectors.
Does a successful network outcome prove the task succeeded?
No. A network outcome describes the call path. Read the transcript evidence actually captured 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 tokens.
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 Cursor’s own documentation and ClawCall’s product documentation, checked on the dates below.

  1. Cursor: Model Context ProtocolOfficial host documentation · checked
  2. CNBC: Cursor 2026 Disruptor 50 profileIndependent market analysis · checked
  3. ClawCall: Hosted MCP for AI agentsClawCall documentation · checked
  4. ClawCall securityClawCall security · checked

Related pages

Can Cursor make phone calls?OpenAI Codex setup guideClaude setup guideHow to give your AI agent a phone numberAll 12 setup guidesFor AI agentsAI phone call APIAI phone calls with ClawCallAPI docsSecurity

Give Cursor a phone line

Create a ClawCall account, add the endpoint, and start with the read-only check. The trial includes 30 calls and 30 minutes, whichever lasts later.

Start freeAll setup guides
Text ClawCall