Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Dialpad to Claude Code

Let Claude send messages and place calls from your Dialpad number. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Dialpad to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Dialpad, you add a Dialpad MCP server: a small hosted service that exposes Dialpad's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Dialpad account. No API keys pasted into config files.

claude mcp add --transport http dialpad https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Dialpad once connected?

Full read-write Dialpad access lets Claude send an SMS or team message, trigger an outbound call from your number, update a contact, and act on a transcript or voicemail once you approve. The follow-up and logging that used to mean switching apps happen where the conversation already lives.

  • Send an SMS or team chat message to a contact or channel
  • Trigger an outbound call from your Dialpad number after you confirm
  • Create or update a contact with details pulled from a transcript
  • Send a follow-up text drawn from a recent call summary
  • Add a tag or label to a call record once a conversation wraps

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Dialpad access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Dialpad API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Dialpad changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Dialpad connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Dialpad connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Dialpad account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Dialpad's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Dialpad?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Dialpad account it signs in with. Revoking access is one click in Dialpad.

More on the Dialpad connector

Dialpad connector for claude.aiTelegram + Claude CodeWhatsApp Business + Claude CodeWebex + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us