built by the makers of Gamut
Getting started

Install DialMCP.

Updated August 17, 2026

Use the direct connection when your client supports remote MCP servers over Streamable HTTP. Use the connector when your client only supports local stdio servers. Building your own server instead? Read how to build an MCP server.

Option 1: connect directly

Point your MCP client at this endpoint:

URL:        https://mcp.dialmcp.com/mcp
Transport:  Streamable HTTP
Auth:       OAuth 2.1

There is no API key to copy. On first connection, DialMCP opens a browser sign-in flow. Verify your phone number by SMS, then return to your client.

Option 2: use the stdio bridge

The bridge is for clients that cannot connect to a remote MCP server. It runs locally and proxies requests to the hosted endpoint.

npx dialmcp-connector

Or add it to a client that accepts an MCP server configuration:

{
  "mcpServers": {
    "dialmcp": {
      "command": "npx",
      "args": ["-y", "dialmcp-connector"]
    }
  }
}

The bridge requires Node.js 18 or newer. It does not contain the calling service; it is a transport shim that starts the OAuth browser flow and forwards MCP traffic.

What happens next

  1. Complete OAuth sign-in in the browser.
  2. Verify a US or Canadian mobile number by SMS.
  3. Your verified number becomes the caller ID for calls you authorize.
  4. Ask your agent to use place_call, then poll the returned call ID with get_call.
Important: DialMCP is designed for individual, objective-driven calls. Bulk calling, telemarketing, surveys, lead generation, debt collection, and political outreach are prohibited. See the safety page.

For ready-to-paste configurations, continue to client setup. For the authentication details, read OAuth and phone verification.