Clawcall
Let your agent initiate and manage AI-powered outbound phone calls in the US through ClawCall’s REST API via stdio MCP.
Overview
ClawCall is an MCP server for the Build phase that connects agents to AI-powered US phone calling through the ClawCall REST API.
What is this MCP server?
- stdio MCP npm package @clawcall/mcp (v0.1.0) for Claude Code–style clients
- AI-powered US phone calling exposed as agent tools on top of ClawCall REST
- CLAWCALL_API_KEY optional—auto-provisioned on first call if unset; env shadows saved key file when set
- CLAWCALL_BASE_URL override defaults to https://api.clawcall.dev
- Source repo subfolder mcp on github.com/ClawCall-Dev/clawcall
- MCP package version 0.1.0 (@clawcall/mcp)
- Default REST base URL https://api.clawcall.dev
- stdio transport via npm registry
Community signal: 7 GitHub stars.
What problem does it solve?
You want voice outreach in an agent workflow but dread maintaining auth, base URLs, and tool definitions for a telephony API by hand.
Who is it for?
Builders shipping US-only voice bots, warm-lead dialers, or internal agents that must place phone calls from Claude Code or Cursor.
Skip if: International calling requirements, teams that cannot use cloud telephony, or products that need full contact-center UI without ClawCall.
What do I get? / Deliverables
Installing @clawcall/mcp lets your agent trigger US calls via MCP tools with keys that can bootstrap on first use.
- MCP tools backed by ClawCall US calling API
- Configurable API base URL and secret key handling
- Agent-driven call workflows without custom REST glue
Recommended MCP Servers
Journey fit
Telephony MCP belongs on Build when you connect voice workflows to the product you are coding, not when you are only brainstorming positioning. Phone calling is a third-party API integration—the MCP package bridges your agent to ClawCall’s calling stack over stdio.
How it compares
Telephony API MCP bridge, not a prebuilt sales playbook skill or CRM marketplace.
Common Questions / FAQ
Who is ClawCall MCP for?
ClawCall MCP is for developers who want MCP-native tools so coding agents can run AI-powered phone calls in the United States through ClawCall.
When should I use ClawCall MCP?
Use it while building agent or SaaS features that must place or automate US phone calls and you already standardize on MCP for external services.
How do I add ClawCall to my agent?
Install the npm package @clawcall/mcp, configure stdio MCP in your client, and set CLAWCALL_API_KEY if needed (optional—first call can auto-provision); optionally set CLAWCALL_BASE_URL.