
ClawdCall
io.github.dialgoodianPublished by GitHub account dialgoodianv0.1.0Updated Nov 2, 2026
Give AI agents a phone layer for consent-based calls, transcripts, summaries, and outcomes.
Overview
ClawdCall gives an AI assistant a phone layer: sign up by OTP, place expected outbound voice calls, and fetch call transcripts.
- What you can do
- Sign up and verify a phone number with one-time passcodes
- Place expected outbound voice-agent calls to a recipient
- Fetch call transcripts by call ID or campaign ID
- Review returned status, transcript evidence, summary or structured outcome
- When to use it
- Use it when an assistant needs to make a consent-based, expected phone call to a known recipient and then read back the transcript or outcome, for example a bounded internal check-in or an alert handoff. It is not meant for cold calling, bulk outreach or emergency use.
- Requirements
- A remote Streamable HTTP endpoint with OAuth, or the local npm package run through npx with Node.js. The CLAWDCALL_API_KEY environment variable is required for outbound calls and transcript retrieval; signup OTP tools work without an existing key. CLAWDCALL_BASE_URL optionally overrides the API base URL.
Installation
In SourceWeft
- Open ClawdCall in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.dialgoodian%2Fclawdcall-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"clawdcall": {
"type": "http",
"url": "https://gateway.clawdcall.com/mcp/"
}
}
}README
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:
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:
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:
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
Environment Variables
Development
Build:
Run the built server:
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
Source: README.md at commit 18b1eeb
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts