About ClawdCall
ClawdCall MCP Server connects AI agents to ClawdCall’s phone execution API for consent-based outbound calls. It supports signup verification and lets agents retrieve call transcripts and outcomes.
Key features
- 01Send and verify signup OTPs
- 02Place expected outbound calls
- 03Retrieve call transcripts
- 04Review call status and outcomes
Use cases
- 01Verify a phone number during signup
- 02Make an approved call to an internal recipient
- 03Review a call transcript and result
MCP support
Exposes ClawdCall signup OTP, outbound calling, and transcript retrieval endpoints as tools for MCP clients. It can run as a hosted remote server or as a local stdio package.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.clawdcall.com/mcp/claude mcp add --transport http dialgoodian-clawdcall https://gateway.clawdcall.com/mcp/{"mcpServers":{"dialgoodian-clawdcall":{"type":"http","url":"https://gateway.clawdcall.com/mcp/"}}}Open in Cursor{"servers":{"dialgoodian-clawdcall":{"type":"http","url":"https://gateway.clawdcall.com/mcp/"}}}Open in VS Code{"mcpServers":{"dialgoodian-clawdcall":{"type":"http","url":"https://gateway.clawdcall.com/mcp/"}}}{"mcpServers":{"dialgoodian-clawdcall":{"serverUrl":"https://gateway.clawdcall.com/mcp/"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEClawdCall 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:
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:
{
"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:
{
"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:
- MCP self-call
- OpenAI Agents SDK
- LangGraph-backed agents
- Signed webhook-to-call alerts
- Flight-change decision handoff
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
git clone https://github.com/dialgoodian/clawdcall-mcp.git
cd clawdcall-mcp
npm install
npm run dev
Build:
npm run build
Run the built server:
CLAWDCALL_API_KEY=your_clawdcall_api_key npm start
Discovery Metadata
server.jsoncontains 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-otpPOST /cc/signup/verify-otpPOST /external/v1/agent/outbound?conversionFlag=1GET /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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.