Your phone system, on MCP. Ask Claude about your calls. Rewrite your routing from chat.
The MCP server exposes your whole phone system – calls, transcripts, voicemails, contacts, routing – as 35 tools any AI assistant can use. Connect once, then just ask.
Any calls I should return from this morning?
▶ list_calls state=lost since=09:00
▶ get_call id=c_8231
One. Sofia Jensen called at 9:41 about order #1042 – she asked for a call back before noon. The other two missed calls left voicemails that don't need action.
Paste the URL. Sign in. Ask. Claude does the rest.
No API keys to copy, no config files, no local server to run. Add one connector URL in your assistant's settings. It opens a browser window for you to sign in to Phone.inc — approve access once and every tool is ready.
https://app.phone.inc/mcp
Claude
- 1Open Settings → Connectors.
- 2Add a custom connector and paste the URL.
- 3Click Connect, sign in to Phone.inc, and approve access.
Using Cursor or another client? See the setup guide for API-key and advanced options.
What it feels like
Add connector
Connected to Phone.inc
35 tools ready in your assistant
“List my business numbers.”
Your assistant can start asking right away.
An MCP server makes your phone speak AI. Not through copy-paste. Through tools.
You already work next to an AI assistant all day. But it has no idea who called your business this morning, what they said, or when your line closes. The MCP server fixes that: it hands your assistant the same 35 operations the API exposes – as tools it can call while you talk to it.
Your AI reads your calls
Transcripts, voicemails, caller history, and context from your integrations – all exposed as tools your assistant can call mid-conversation, without you exporting anything.
It writes, too
Business hours, routing rules, contacts, and webhooks are writable tools. “We're closed Friday afternoon” becomes a config change, not a support ticket.
Sign in once
Claude walks you through OAuth automatically. Paste the URL, approve access in your browser, and you're connected — no API keys to generate or config files to edit.
One protocol, every assistant
MCP is an open standard. Connect Claude today and whatever your team adopts next year – same endpoint, same 35 tools.
Things you'll actually ask. Once your assistant can reach the phone.
The morning debrief
“What happened on the phone yesterday?” Your assistant lists the calls, reads the transcripts, and gives you the three that need a call-back.
The context puller
Writing a proposal in Claude? Ask what the customer said on their last three calls and quote them their own words.
The schedule keeper
“We're at a trade fair Thursday and Friday.” The assistant updates your business hours and sets the outside-hours message in one go.
The voicemail triager
“Anything urgent in the voicemails?” It reads all of them, flags the two that matter, and drafts your replies.
The contact janitor
Paste a signature, a text thread, or an email – “add these people to contacts” – and the address book updates itself.
The onboarding shortcut
“Invite Maria to the phone system and add her to the support group.” One sentence instead of a settings safari.
35 tools. Zero surprises. Every one mirrors the public API.
Calls with transcriptions on get_call, voicemails, contacts, employees, business numbers with call-flow configs, caller context, webhooks, and company settings. Every tool mirrors a public API endpoint.
Business numbers
Calls
Voicemails
Caller context
Contacts
Employees
Webhooks
Company
MCP
Hand your AI the phone.
Every account comes with the MCP server. When your batch opens, add the URL in Claude, sign in once, and ask your first question.