Purpose
ClawdCall MCP Server is designed to let AI agents access ClawdCall's agent-facing telephony execution API through the Model Context Protocol (MCP). Its public workflow is limited to: sending a registration OTP, verifying a registration OTP, initiating an expected outbound call, and retrieving call records.
Main capabilities
The server exposes the following ClawdCall agent-facing interfaces:
- POST /cc/signup/send-otp
- POST /cc/signup/verify-otp
- POST /external/v1/agent/outbound?conversionFlag=1
- GET /cc/v1/calls/{id}/transcript
Supported flows include: sending a registration OTP, verifying a registration OTP, initiating an expected outbound call, and retrieving call records. Remote MCP clients can connect to a Streamable HTTP endpoint, which publishes OAuth protected resource metadata; existing ClawdCall integrations can also use an API key according to the agent documentation. A local Stdio package is also available for installation into local MCP clients via npm.
Usage
Local Stdio package: add the published npm package to a local MCP client. Environment variables: CLAWDCALL_API_KEY is required for outbound calls and retrieving call records; the registration OTP tools do not require an existing key. To route to staging or a self-hosted API, use the corresponding environment variables.
Safe first test steps (officially provided):
- Open ClawdCall agent settings.
- Connect the hosted endpoint or local package from a compatible agent client.
- Ask the agent to call you or the intended internal recipient with a bounded task.
- Confirm the destination and task before allowing the call.
- Review the returned status, call record evidence, summary, or structured result.
Copy-paste examples: the examples directory contains bounded first-call workflows, suitable for the OpenAI Agents SDK, LangGraph-supported agents, signed webhook to call alerts, and flight change decision handoff. The code examples place the recipient in an operator-controlled environment variable; agent-generated input cannot change the phone number, and the action that actually takes effect requiresexplicit approval or opt-in.
Discovery metadata: server.json contains Official MCP Registry metadata. There is also agent-readable documentation and an OpenAPI description.
Applicable scenarios
Suitable for scenarios that initiate expected outbound calls with user consent and retrieve call records, summaries, and results, such as bounded call flows like internal task handoff or flight change decision handoff.
Limitations
ClawdCall is not suitable for cold calling, robocalling, bulk outreach, emergency use, political outreach, or sensitive advice workflows. Before the relevant routes appear in its API contract, MCP tools should not be added for agents, number purchase, SMS, sessions, voice, or generic webhooks.
