AgentPhone
AgentPhone is an MCP server published by AgentPhone; its MCP spec-revision support has not been verified yet. It is the first-party server from AgentPhone. Last verified 2026-09-03.
Does AgentPhone support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision AgentPhone supports (as of 2026-09-03).
Is AgentPhone a first-party (official) MCP server?
Yes. AgentPhone is the first-party MCP server published by AgentPhone (last verified 2026-09-03).
How do I connect to AgentPhone?
AgentPhone is available via a hosted remote endpoint at https://mcp.agentphone.ai/mcp, the package npm:agentphone-mcp, the official MCP Registry under io.github.AgentPhone-AI/agentphone, the source repository at https://github.com/AgentPhone-AI/agentphone-mcp. Authentication: api_key. Transports: streamable-http, stdio.
What tools does AgentPhone expose?
AgentPhone exposes 28 tools, including buy_number, list_numbers, send_message, get_messages, make_call, list_calls (last verified 2026-09-03).
When were AgentPhone's facts last verified?
2026-09-03. Each fact on this page links to the sources used to verify it.
Which tools does AgentPhone expose?
28 tools verified.
buy_numberlist_numberssend_messageget_messagesmake_calllist_callscreate_agentset_webhook
AgentPhone's first-party MCP server for its own telephony API. It gives an agent a real phone number and the tools to use it: buying and listing numbers, sending and reading SMS, placing calls, managing voice agents and their attached numbers, and configuring webhooks, across 28 tools. The company's backend is the only intermediary to the carrier network, and numbers and messages are metered, so this is a paid service rather than a local utility.
Two access paths are documented: the vendor-hosted endpoint at
mcp.agentphone.ai/mcp over Streamable HTTP with a bearer API key, and a
local stdio bridge from npm:agentphone-mcp reading AGENTPHONE_API_KEY.
The README also documents an OAuth authorization-code flow with PKCE
proxied to AgentPhone's authorization server as the recommended path for
end users.
A probe on 2026-09-03 found the hosted endpoint live and refusing
uncredentialed calls: both a current-revision server/discover and a
legacy initialize returned 401 with "Missing Authorization header". That
grounds the endpoint and its auth requirement but negotiates no protocol
revision, so spec support remains unverified.
Authority is first-party on the vendor's own evidence: agentphone.ai
documents MCP support, shows the package in a client config, and links the
publishing organization, and the hosted endpoint is on the vendor's own
domain. Two identity mismatches are recorded rather than smoothed over:
the registry name ends in agentphone while the repository and package
are both agentphone-mcp, and the registry record still pins 0.6.0 from
2026-06-25 while npm has shipped 0.7.0 since 2026-08-25.
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.AgentPhone-AI/agentphone, fetched 2026-09-03 - version 0.6.0 published 2026-06-25, package npm agentphone-mcp 0.6.0 with stdio transport, remote streamable-http https://mcp.agentphone.ai/mcp - accessed
- AgentPhone site, fetched 2026-09-03 - states "Native MCP support" and shows an MCP client config invoking the agentphone-mcp package, and links the publishing GitHub organization; a server fronting the publisher's own telephony product, which establishes first_party authority - accessed
- Endpoint probe 2026-09-03 - both server/discover with MCP-Protocol-Version 2026-07-28 and a legacy initialize returned HTTP 401 with body {"error":"Missing Authorization header"}; the vendor's hosted endpoint is live and requires a bearer token, and no protocol revision was negotiated - accessed
- Repository README, fetched 2026-09-03 - "Give AI agents real phone numbers, SMS, and voice calls via the Model Context Protocol"; documents the hosted Streamable HTTP endpoint with an Authorization bearer header, a local stdio mode via npx with AGENTPHONE_API_KEY, and lists 28 tools across account, numbers, SMS, contacts, calls, agents and webhooks - accessed
- Repository metadata, fetched 2026-09-03 - AgentPhone-AI/agentphone-mcp, MIT, 121 stars, created 2026-02-26, last push 2026-08-29, not archived, no published security advisories; the repository name differs from the registry name's trailing segment - accessed