ClawdCall MCP Server

Give AI agents access to ClawdCall's agent-facing phone execution API through the Model Context Protocol.

clawdcall-mcp exposes the confirmed ClawdCall workflow:

send signup OTP
verify signup OTP
place expected outbound calls
fetch call transcripts

Hosted Remote

Connect compatible remote MCP clients to the Streamable HTTP endpoint:

text

https://gateway.clawdcall.com/mcp/

The endpoint advertises OAuth protected-resource metadata. Existing ClawdCall integrations may also use an API key according to the agent documentation.

Local Stdio Package

Add the published npm package to a local MCP client:

config.json

{
  "mcpServers": {
    "clawdcall": {
      "command": "npx",
      "args": ["-y", "clawdcall-mcp"],
      "env": {
        "CLAWDCALL_API_KEY": "your_clawdcall_api_key"
      }
    }
  }
}

CLAWDCALL_API_KEY is required for outbound calls and transcript retrieval. Signup OTP tools do not require an existing key.

For staging or self-hosted API routing:

config.json

{
  "mcpServers": {
    "clawdcall": {
      "command": "npx",
      "args": ["-y", "clawdcall-mcp"],
      "env": {
        "CLAWDCALL_API_KEY": "your_clawdcall_api_key",
        "CLAWDCALL_BASE_URL": "https://api.clawdcall.com"
      }
    }
  }
}

Safe First Test

Open the ClawdCall agent setup.
Connect the hosted endpoint or local package from a compatible agent client.
Ask the agent to call you or an expected internal recipient with a bounded task.
Confirm the destination and task before allowing the call.
Review the returned status, transcript evidence, summary, or structured outcome.

ClawdCall is not intended for cold calling, robocalling, bulk outreach, emergency use, political outreach, or sensitive advice workflows.

Copy-Paste Examples

The examples directory contains bounded first-call workflows for:

The code examples keep the recipient in operator-controlled environment variables. Agent-generated input cannot change the phone number, and live side effects require an explicit approval or opt-in.

Tools

Tool	Confirmed endpoint	Description
`send_signup_otp`	`POST /cc/signup/send-otp`	Send a phone verification OTP for signup.
`verify_signup_otp`	`POST /cc/signup/verify-otp`	Verify the OTP and receive account/API-key details.
`place_outbound_call`	`POST /external/v1/agent/outbound?conversionFlag=1`	Place an expected outbound voice-agent call.
`get_call_transcript`	`GET /cc/v1/calls/{id}/transcript`	Fetch a transcript by call ID or campaign ID.

Environment Variables

Variable	Required	Default	Description
`CLAWDCALL_API_KEY`	For call/transcript tools		ClawdCall API key.
`CLAWDCALL_BASE_URL`	No	`https://api.clawdcall.com`	API base URL.

Development

bash

git clone https://github.com/dialgoodian/clawdcall-mcp.git
cd clawdcall-mcp
npm install
npm run dev

Build:

Terminal

npm run build

Run the built server:

bash

CLAWDCALL_API_KEY=your_clawdcall_api_key npm start

Discovery Metadata

server.json contains the Official MCP Registry metadata.
Server card
Agent-readable documentation
OpenAPI description

API Contract

This server tracks these ClawdCall agent-facing endpoints:

POST /cc/signup/send-otp
POST /cc/signup/verify-otp
POST /external/v1/agent/outbound?conversionFlag=1
GET /cc/v1/calls/{id}/transcript

Do not add MCP tools for agents, number purchase, SMS, conversations, voices, or general webhooks until those routes exist in ClawdCall's API contract.

License

MIT