Callmcp MCP

Name: Callmcp MCP
Author: CallMCP

by CallMCPversion 0.1.2i★ –iRuns on your computer

Registry nameai.callmcp/server

Install

Overview

Description from the maker (original English)

One MCP tool contract for telephony — any call provider, hosted, local, or BYOK.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CALLMCP_CONFIG, CALLMCP_DEFAULT_DRIVER

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "server": {
      "command": "npx",
      "args": [
        "-y",
        "@callmcp/server"
      ],
      "env": {
        "CALLMCP_CONFIG": "your-value",
        "CALLMCP_DEFAULT_DRIVER": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add server --env CALLMCP_CONFIG=your-value --env CALLMCP_DEFAULT_DRIVER=your-value -- npx -y @callmcp/server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "server": {
      "command": "npx",
      "args": [
        "-y",
        "@callmcp/server"
      ],
      "env": {
        "CALLMCP_CONFIG": "your-value",
        "CALLMCP_DEFAULT_DRIVER": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "server": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@callmcp/server"
      ],
      "env": {
        "CALLMCP_CONFIG": "your-value",
        "CALLMCP_DEFAULT_DRIVER": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CALLMCP_CONFIG env
Path to a callmcp.config.json file. Omit to configure entirely via env vars.
CALLMCP_DEFAULT_DRIVER env
driver_id routed to when a tool call omits `driver` (e.g. kaicalls, dograh, twilio_openai).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain callmcp.ai (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32415 servers in this category
Published to the registry more recently than 17% of the other 32415 servers in this category
Basic checks equal to or better than 100% of the other 32415 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Callmcp MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Safe Fetch

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Safe Fetch

by Sanoy24

MCP server for fetching URLs, safe against SSRF, DNS rebinding, and redirect-to-internal attacks.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

One MCP server. Any call provider. Fully local, fully hosted, or bring your own frontier model.

CallMCP is a single Model Context Protocol server that defines one tool contract — 14 tools, identical schemas, identical error shapes — for outbound/inbound telephony: calls, SMS, recordings, transcripts, and phone-number lifecycle. Point it at a hosted backend, a fully local backend, or a bring-your-own-key composed backend, and your agent code doesn't change. What changes is *which* tools are present (via capability-gated dynamic discovery), never the shape of a tool that's there.

The normative reference is SPEC.md. This README is the pitch; the spec is the contract.

npx -y @callmcp/server

Before connecting a real provider, run npx -y @callmcp/server doctor. For a safe local walkthrough, run npx -y @callmcp/server --sandbox. The server fails closed when no driver is configured; the mock driver is only available through explicit sandbox configuration.

See examples/ for ready-to-paste Claude Desktop / Claude Code configs for each of the three legs below.

Three structural claims

This isn't "a Twilio wrapper with a marketing page." Three things are actually built into the contract, not bolted on:

1. Provider-neutral, multi-backend contract

Every driver — hosted, local, or BYOK — implements the same 14 tools defined in SPEC.md. Driver-specific behavior lives exclusively inside a namespaced options. passthrough object. There is no make_call_twilio or make_call_kaicalls. A tool either exists for your configured driver (and works, fully, per spec) or it's absent from tools/list — never present-but-broken. Swapping your call backend is a config change, not a rewrite.

2. x402-funded autonomous provisioning to production

search_numbers, buy_number, configure_number, and list_numbers are never human-approval-gated — they don't contact a third party, they contact your own provider account. That includes settling cost via x402 machine payments when a driver requires prepayment (INSUFFICIENT_FUNDS embeds a full x402 challenge an agent can settle and retry). An agent can search for a number, pay for it, configure it, and go live — autonomously, in production, with real money — without a human clicking anything. This is a deliberate contrast with vendor MCPs whose autonomous/self-serve paths are trial- or sandbox-scoped only.

3. Human-in-the-loop outbound approval as designed consent architecture

make_call and send_sms — anything that contacts a phone number that isn't the calling agent's own infrastructure — structurally require a valid approval_id or a standing allowlist match before they act. This isn't a policy suggestion layered on top; it's enforced in the server core, so no driver implementation can bypass it. Primary path is MCP elicitation; the fallback for non-elicitation clients is a single-use out-of-band approval URL — the gate is designed to never silently block forever *and* never silently open. Read as a TCPA-consent posture: the contract makes "who approved contacting this number, and when" a first-class, auditable object (request_call_approval / list_approvals), not an assumption baked into application code you have to get right yourself.

CallMCP vs. single-vendor MCPs vs. DIY

Capability	CallMCP	Vapi MCP	Telnyx MCP	AgentPhone MCP	DIY (Twilio + your own glue)
Tool contract	One schema, 14 tools, portable across backends	Single-vendor, Vapi only	Single-vendor, Telnyx only	Single-vendor, AgentPhone only	No contract — you write and maintain it
Swap call backend without rewriting agent code	Yes — driver swap only	No	No	No	No
Self-hostable / fully local option	Yes (Dograh driver)	(unverified, recheck before publishing)	(unverified, recheck before publishing)	(unverified, recheck before publishing)	Yes, but you own the entire stack
Bring your own frontier model as the call's "brain"	Yes (BYOK driver: any transport + any LLM)	(unverified, recheck before publishing)	(unverified, recheck before publishing)	(unverified, recheck before publishing)	Yes, fully manual integration
Autonomous, funded, production-scoped number provisioning (x402)	Yes — `search_numbers`/`buy_number`/`configure_number` ungated, x402-payable	(unverified, recheck before publishing)	Public self-serve docs read as trial-scoped autonomy, not funded production autonomy (unverified, recheck before publishing)	(unverified, recheck before publishing)	No — manual console purchase, manual compliance
Outbound approval / consent gate structural in the schema	Yes — `make_call`/`send_sms` require `approval_id` or allowlist match, enforced server-side	(unverified, recheck before publishing)	(unverified, recheck before publishing)	(unverified, recheck before publishing)	No — you build and maintain your own gate
Standalone SMS (not agent-mediated only)	Capability-gated per driver, honestly reported — never claimed where it's actually agent-mediated	(unverified, recheck before publishing)	Yes, native	(unverified, recheck before publishing)	Yes, native Twilio API
Call recording	Capability-gated per driver, honestly reported	(unverified, recheck before publishing)	(unverified, recheck before publishing)	(unverified, recheck before publishing)	Yes, native Twilio API
Real-time transcript streaming	Capability-gated per driver, subscribable resource when supported	(unverified, recheck before publishing)	(unverified, recheck before publishing)	(unverified, recheck before publishing)	DIY — you build the capture/assembly layer
Source availability	MIT-licensed server + Apache-2.0 spec, public monorepo	(unverified, recheck before publishing)	(unverified, recheck before publishing)	(unverified, recheck before publishing)	N/A — it's your own code
Markup over underlying carrier cost	Zero in the OSS server — it routes at cost; KaiCalls hosted tier is an optional convenience layer, not a requirement	(unverified, recheck before publishing)	(unverified, recheck before publishing)	(unverified, recheck before publishing)	Zero markup, 100% of integration cost is yours

Every "(unverified, recheck before publishing)" cell is a placeholder, not a claim — we do not put a number or a fact about a competitor's product in this table without a citation behind it. If you're reading this before that recheck has happened, treat those cells as unknown, not as "no."

Who builds this, and what's actually free

CallMCP is built and maintained by CallMCP / KaiCalls. Full transparency, because hiding this costs more credibility than stating it:

This OSS server is not a loss-leader funnel with the real functionality locked behind a paywall. It routes to any configured driver — hosted, local, or BYOK — with no markup and no artificial capability gating. A self-hosted Dograh driver or a BYOK Twilio+LLM driver gets the exact same 14-tool contract as the KaiCalls driver.
KaiCalls is the hosted default — the path of least resistance if you want a call backend running in minutes with nothing to self-host. It is not the *only* supported path, and the spec and conformance suite exist precisely so that claim stays true as the driver ecosystem grows.
The driver interface is public and the conformance suite runs in CI. Any driver — including ones we didn't write — can claim conformance, and community PRs are held to the same bar KaiCalls' own driver is held to (see SPEC.md §6).

If any of the above stops being true, that's a bug in this README, not a hidden asterisk — open an issue.

Driver capability matrix

Capability is expressed by *presence*, not by runtime errors (see SPEC.md §2.2). This table mirrors the spec's degradation appendix (SPEC.md §7) — the honest state of the wider backend landscape at spec-writing time (2026-07-09), not a ceiling on what CallMCP itself can do.

Launch drivers (this repo)

Capability	`kaicalls` (hosted)	`dograh` (local)	`twilio_openai` (BYOK)
`make_call` / `end_call` (hangup)	Yes — hangup via Vapi `controlUrl`, treated as call-scoped state	`make_call` yes; no external hangup endpoint (`supports_hangup: false`)	Yes, native Twilio call control
`search_numbers` / `buy_number` / `configure_number`	Yes	No purchase flow — BYO carrier account (`supports_number_purchase: false`)	Yes, native Twilio number API
`send_sms`	Capability-gated on the underlying Vapi-class backend; not claimed unless a real standalone send path exists	No SMS capability	Yes, native Twilio SMS
`get_recording`	Yes, once wired	Capability-dependent on the local stack	Yes, native Twilio recording
`get_transcript` / realtime streaming	Yes	Yes, baseline (Dograh's `GET /{workflow_id}/runs/{run_id}` returns `transcript_url` — the one fully source-verified transcript path in the wider landscape)	DIY assembly from realtime session events; `supports_realtime_transcription` only claimed once that assembly is genuinely live

Known gaps across the wider backend landscape (context for driver authors)

Tool / capability	Known gaps at spec-writing time
`buy_number`	Absent on Synthflow (UI-only, no API), ElevenLabs (BYO-number only), Dograh (BYO carrier), Phonely (not independently drivable)
`end_call`	Absent on Retell and Synthflow (no hangup endpoint); Dograh has no external hangup endpoint; Vapi supports it only via a per-call ephemeral `controlUrl`, not a stable REST endpoint
`send_sms`	The most degraded tool in the whole contract. Only Telnyx, Bland, Autocalls, and Thoughtly expose real standalone SMS. Vapi/Retell/Synthflow are agent-mediated only (not a stable API surface, never claimed as `supports_sms: true`). Millis, Vogent, and Dograh have no SMS capability at all. AgentLine's own public materials contradict themselves on this (`SKILL.md` forbids SMS while its API spec defines `POST /v1/messages`) — cited as unresolved upstream, not resolved on AgentLine's behalf
`get_recording`	Absent on AgentLine entirely; LiveKit-based backends require standing up a separate Egress service before it's real
`get_transcript` (realtime)	LiveKit/Pipecat-local stacks require DIY event capture; Bolna's transcript endpoint is unconfirmed; Telnyx's exact transcript route is unverified

A driver claiming a capability it can't demonstrate against the conformance suite fails CI (see SPEC.md §6.2) — this table is a snapshot, not a promise about backends CallMCP doesn't control, and any driver author whose backend's real capability differs from this snapshot updates their own manifest, not this README.

Repo shape

callmcp/callmcp

├── SPEC.md canonical tool contract (start here) ├── packages/ │ ├── server/ @callmcp/server — MCP core: transports, driver │ │ registry, config resolution, approval state │ │ machine, elicitation + fallback-URL flow, │ │ dynamic tools/list │ ├── driver-interface/ @callmcp/driver-interface — TS interface, │ │ capability manifest types, conformance test harness │ ├── driver-kaicalls/ hosted default driver │ ├── driver-dograh/ local/self-hosted dr

Only the beginning is shown; read the rest in the repo

Callmcp MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Safe Fetch

README from the maker

One MCP server. Any call provider. Fully local, fully hosted, or bring your own frontier model.

Three structural claims

1. Provider-neutral, multi-backend contract

2. x402-funded autonomous provisioning to production

3. Human-in-the-loop outbound approval as designed consent architecture

CallMCP vs. single-vendor MCPs vs. DIY

Who builds this, and what's actually free

Driver capability matrix

Launch drivers (this repo)

Known gaps across the wider backend landscape (context for driver authors)

Repo shape