clawdcall-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAWDCALL_API_KEY | No | ClawdCall API key. Required for outbound calls and transcript retrieval. | |
| CLAWDCALL_BASE_URL | No | API base URL. | https://api.clawdcall.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_signup_otpA | Send a ClawdCall signup phone verification OTP. Does not require an API key. |
| verify_signup_otpA | Verify a ClawdCall signup OTP and receive account/API-key details. Does not require an existing API key. |
| place_outbound_callB | Place an outbound ClawdCall agent call. Requires CLAWDCALL_API_KEY. |
| get_call_transcriptA | Fetch a ClawdCall transcript by call ID or campaign ID. Requires CLAWDCALL_API_KEY. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: two are sequential OTP signup steps, one places a call, and one fetches a transcript. There is no real overlap or ambiguity between them.
All tool names follow a consistent snake_case verb_noun pattern: send_, verify_, place_, get_. The naming style is uniform and predictable.
Four tools is a well-scoped count for a focused server. Each tool earns its place in the signup-and-call workflow without unnecessary bloat or thinness.
The signup OTP flow, outbound call placement, and transcript retrieval form a coherent end-to-end workflow. Minor gaps exist, such as call status, cancellation, or listing, but agents can work around them for the core use case.