The Phone.inc MCP server
Your phone system, on MCP. Ask Claude about your calls. Let ChatGPT rewrite your routing.
The MCP server exposes your whole phone system — calls, transcripts, voicemails, contacts, routing — as thirty 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_transcription 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.
The value
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 thirty 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
- Opening hours, routing rules, contacts, and webhooks are writable tools. “We're closed Friday afternoon” becomes a config change, not a support ticket.
- Scoped like your API key
- The MCP server reuses your API keys and OAuth. Hand your assistant a read-only key and it gets a read-only tool list — write tools simply aren't there.
- One protocol, every assistant
- MCP is an open standard. Connect Claude today, ChatGPT tomorrow, and whatever your team adopts next year — same endpoint, same thirty tools.
Connect
Connected in a minute. One endpoint, your existing API key.
The server speaks streamable HTTP — no local process, nothing to install. Point your client at the endpoint, authenticate with an API key or OAuth, and the tools show up.
mcp.json
{
"mcpServers": {
"phone-inc": {
"url": "https://app.phone.inc/mcp",
"headers": {
"Authorization": "Bearer $API_KEY"
}
}
}
}
Ideas to try
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 opening 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.
The tools
Thirty tools. Zero surprises. Every one mirrors the public API.
Calls with full transcriptions, voicemails, contacts, employees, main numbers with their call-flow configs, caller context, webhooks, and your company settings. Read-only API keys see only the read tools — the write tools aren't hidden, they're gone.
MCP
Hand your AI the phone.
Every account comes with the MCP server. Generate a key in the dashboard, paste one URL into your assistant, and ask your first question.