MCP server: run Call2Me from ChatGPT or Claude
Connect Call2Me to any MCP client and place calls, read transcripts, manage interpreters and buy numbers in plain language. 37 tools behind OAuth 2.1 with PKCE — your API key never reaches the model.
Updated October 2, 2026
The MCP server exposes your Call2Me account to an AI assistant as a set of tools. Once connected, you ask for what you want — "read me the transcript of my last call", "buy a US number for this agent" — and the assistant calls the API on your behalf.
Server URL:
https://mcp.call2me.app/mcp
Connecting
- In your MCP client, add a connector and paste the server URL above.
- Your browser opens our sign-in page. Approve the scopes you want.
- Ask for something. Start with "list my agents" — it is read-only, so nothing can go wrong while you look around.
There is no separate API key to paste and no config file to edit. The authorisation step hands the server a token bound to your account; the key it uses on your behalf stays encrypted on our side.
Scopes
| Scope | What it allows |
|---|---|
call2me:read | Everything read-only: profile, agents, calls, transcripts, numbers, campaigns, schedules, wallet, interpreters, pricing |
call2me:write | Creating and changing things, placing calls, buying numbers |
Granting only call2me:read is a real restriction, not a hint: the server
rejects every write with a 403 regardless of what the assistant asks for.
Useful for reporting, and for trying it out before you let it touch anything.
The 37 tools
Every tool declares what it does, so a compliant client can decide when to
check with you first. The three annotations are set explicitly on all of them
— the MCP spec defaults destructiveHint and openWorldHint to true, so
leaving them unset would mark harmless read tools as dangerous and bury the
genuinely destructive ones in the noise.
Read-only — 17 tools
call2me_profile · call2me_get_wallet · call2me_get_pricing ·
call2me_list_agents · call2me_get_agent · call2me_list_calls ·
call2me_get_call · call2me_get_call_transcript ·
call2me_list_phone_numbers · call2me_search_numbers ·
call2me_list_allowed_countries · call2me_list_campaigns ·
call2me_list_schedules · call2me_list_interpreters ·
call2me_get_interpreter · call2me_list_interpreter_calls ·
call2me_get_interpreter_web_status
Write — 10 tools
call2me_create_agent · call2me_update_agent · call2me_create_schedule ·
call2me_bind_number · call2me_checkout_number ·
call2me_create_voice_session · call2me_create_interpreter ·
call2me_update_interpreter · call2me_enable_interpreter_web ·
call2me_create_interpreter_passcode
Destructive — 10 tools
These spend money or cannot be undone. A compliant client asks you first.
call2me_make_outbound_call · call2me_end_call ·
call2me_purchase_number · call2me_release_number ·
call2me_unbind_number · call2me_delete_agent ·
call2me_cancel_schedule · call2me_start_interpreter_call ·
call2me_delete_interpreter · call2me_end_interpreter_web
Interpreter support
The interpreter is fully covered — eight of the tools above are interpreter tools. From an assistant you can list and inspect interpreters, create a language pair, enable the browser room, mint a single-use passcode, start a phone session and end a live browser session. See Live interpreter for what the product does and the API reference for the raw endpoints.
Protocol details
| Transport | Streamable HTTP |
| Protocol revisions | 2025-11-25 and 2026-07-28 |
| Auth | OAuth 2.1, PKCE (S256) required |
| Metadata | RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource |
| Token audience | Bound per RFC 8707 — a token minted for another resource is rejected |
Both protocol revisions are served because the transport changed between
them; your client negotiates whichever it speaks via the
MCP-Protocol-Version header.
What it does not do
- It cannot read other tenants' data. Tools run with your account's own permissions, same as your API key.
- It cannot mint more tokens. The access token reaches the MCP tools and nothing else.
- It does not bypass your balance. Calls and numbers draw on the same wallet as the dashboard; an insufficient balance fails the tool call rather than going into debt.
Frequently asked
Q.What is MCP?
The Model Context Protocol is an open standard that lets an AI assistant call external tools. Adding the Call2Me MCP server gives your assistant 37 tools for calls, interpreters and phone numbers, so you ask in plain language instead of writing API requests yourself.
Q.Which clients can connect?
Any MCP client over Streamable HTTP. We serve both the 2025-11-25 and 2026-07-28 protocol revisions, which covers ChatGPT, Claude and the common developer clients.
Q.Does the model ever see my API key?
No. You authorise once through OAuth 2.1 with PKCE and the key is stored encrypted on our side. The assistant receives only the result of a tool call — never the credential.
Q.Can it spend money without asking me?
Placing calls and buying numbers are declared as destructive tools, so a compliant client asks you first. You can also connect with the call2me:read scope only, which cannot write anything at all.
Q.What does the MCP server cost?
Nothing extra. You pay the normal per-minute rate for calls and interpreting and the normal monthly price for any number you buy — the same prices as the dashboard.
Q.How do I disconnect it?
Remove the connector in your assistant. That ends the session; refresh tokens rotate on every use, and a reused token revokes the whole token family.