What this is
DialMCP is a remote MCP server at https://mcp.dialmcp.com/mcp. Any client that speaks
Streamable HTTP with OAuth can connect to
it directly — no install, no API keys. You do not need this package for those clients.
Agenten stärken
Die eigene URL des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
https://mcp.dialmcp.com/mcpDie Claude-Schaltfläche oben öffnet Claude mit ausgefülltem Namen und ausgefüllter URL. Sie bestätigen dort noch.
claude mcp add --transport http com.dialmcp-dialmcp https://mcp.dialmcp.com/mcpRun in a terminal.
{ "mcpServers": { "com.dialmcp-dialmcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.dialmcp.com/mcp" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
DialMCP is a remote MCP server at https://mcp.dialmcp.com/mcp. Any client that speaks
Streamable HTTP with OAuth can connect to
it directly — no install, no API keys. You do not need this package for those clients.
Let AI agents place real phone calls from your verified number, with transcripts and recordings.
This repository exists for two reasons:
dialmcp-connector launches a local stdio server that proxies to the hosted endpoint and
handles the OAuth browser flow for you.server.json registry manifest, and the safety model — in one auditable place.The hosted calling service itself is closed-source. This connector is MIT-licensed and contains no proprietary logic: it is a thin transport shim over a public endpoint.
If your client supports remote MCP servers, skip this package entirely:
URL: https://mcp.dialmcp.com/mcp
Transport: Streamable HTTP
Auth: OAuth 2.1 (sign in with your phone number)
claude mcp add --transport http dialmcp https://mcp.dialmcp.com/mcp
# add --scope user to enable it in every project
[mcp_servers.dialmcp]
url = "https://mcp.dialmcp.com/mcp"
Settings → Connectors → Add custom connector → paste https://mcp.dialmcp.com/mcp.
Settings → Connectors → Add MCP server → paste the URL (HTTP / OAuth) → complete SMS verification.
On first connect a browser window opens for sign-in. Verify your phone number with an SMS code — that number becomes your caller ID.
npx dialmcp-connector
Or in an MCP client config:
{
"mcpServers": {
"dialmcp": {
"command": "npx",
"args": ["-y", "dialmcp-connector"]
}
}
}
See examples/ for ready-to-paste configs.
The API is async by design: place_call returns instantly with a call ID and your agent polls
get_call, so a multi-minute call never trips a client's tool timeout.
When a call completes, get_call returns a structured resolution — achieved, partially_achieved, or
not_achieved — with a summary, any commitments the other party made, suggested follow-ups, a
turn-by-turn transcript, and a signed link to the audio recording.
During the call the service presses keys through automated phone trees, waits silently through hold music, and detects voicemail — hanging up rather than leaving a message.
Every protection is enforced server-side, not as model instructions the agent could talk itself out of.
Full detail: https://dialmcp.com/safety.html
Every release publishes to two places: npm (dialmcp-connector) and the
official MCP Registry (com.dialmcp/dialmcp). Both are
automated by .github/workflows/release.yml.
version in both package.json and server.json — npm run validate:manifest fails if they
disagree, and CI runs it on every push.main.dry_run left checked) and let
it go green. This packs the tarball and validates server.json against the live registry schema without
publishing anything.vX.Y.Z. The tag must match package.json or the workflow stops before
publishing.Step 3 is worth the two minutes: registry versions are immutable and cannot be unpublished. A bad version can only be superseded by a higher one or marked deprecated.
--provenance attaches a signed attestation linking the tarball back to the commit and workflow run that
built it, which is why the job needs id-token: write.
The registry publish is a separate job for two reasons. It has to wait for npm: the registry proves
ownership by fetching the freshly published version and reading its mcpName field, which 404s until npm
propagates (the job retries for ~2.5 minutes). And it holds the signing key, which is scoped to the whole
com.dialmcp namespace rather than this one package — so it lives in a protected environment. Keeping that
environment off the publish job is deliberate: its branch policy only admits v* tags, and applying it
job-wide would block manual dry runs from main outright.
The TXT record goes on the bare domain, SPF-style — a _mcp. selector is not read and fails with an opaque
signature error. Signatures carry a ±15s timestamp window, so the runner's clock must be accurate.
Issues and pull requests are welcome for the connector, docs, and client configs. Bugs in the hosted service itself are best sent to [email protected]. Please read SECURITY.md before reporting anything security-related.
MIT © Datawizz Inc. See LICENSE.
Let AI agents place real phone calls from your verified number, with transcripts and recordings.
{ "mcpServers": { "com.dialmcp-dialmcp": { "url": "https://mcp.dialmcp.com/mcp", "headers": {} } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
DialMCP wird über HTTP erreicht.
Zuletzt geprüft: 2026-10-23. Let AI agents place real phone calls from your verified number, with transcripts and recordings.