
AgentPhone Apex MCP
AgentPhone is a MCP server that provides a multi-channel voice and SMS gateway interface for AI communication.
About
AgentPhone (io.github.Evozim/agent-phone) is a hosted MCP server that advertises a multi-channel voice and SMS gateway interface for AI communication. Developers shipping agent-first products—support bots, appointment reminders, or voice-enabled workflows—can point Claude Code, Cursor, or similar clients at the SSE remote URL instead of embedding separate telco SDKs in every project. The entry is titled AgentPhone-Apex in metadata and ships at version 1.0.0. Because it is remote MCP, you integrate at configuration time: add the endpoint, respect optional payment-signature requirements for paid settlement, and design your prompts or tools around voice and SMS capabilities the server exposes. It is a communication integration layer, not a full CRM or contact-center suite; you still own compliance (TCPA, consent, recording laws) and message content. Use during build when telephony is a first-class channel for your SaaS or internal agent.
- AgentPhone-Apex remote MCP over SSE for multi-channel voice and SMS
- Positions itself as a gateway interface for AI-driven communication
- Catalog version 1.0.0 on the standard MCP server schema
- Premium tier may require payment-signature header on requests
- Fits outbound notifications, IVR-style flows, or human handoff via phone/SMS from agents
AgentPhone Apex MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add --transport sse agent-phone https://agent-phone-mcp.vercel.app/api/mcp --header "payment-signature: YOUR_PAYMENT_SIGNATURE"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | SSE |
|---|---|
| Auth | Required |
What it does
Let coding agents place or manage voice and SMS outreach through one MCP gateway instead of custom telephony SDK glue.
Who is it for?
Best when you're adding call or text capabilities to support, sales, or ops agents via MCP.
Skip if: Products that need only in-app chat with no telephony, or teams barred from using remote third-party comms endpoints.
What you get
After registration, your agent client can reach a unified voice and SMS gateway through standard MCP remote SSE calls.
- MCP-connected voice and SMS channel for your agent workflows
- Reduced custom telephony glue in the build phase
By the numbers
- Version 1.0.0
- One documented remote SSE URL
- Two communication modalities stated: voice and SMS
Recommended MCP Servers
How it compares
Telephony MCP gateway, not a marketing automation skill or local CLI dialer.
FAQ
Who is AgentPhone for?
Developers and small teams building AI agents that must talk to people over voice or SMS through MCP.
When should I use AgentPhone?
Use it while building integrations when your product needs programmatic voice or SMS from an agent without writing a custom gateway first.
How do I add AgentPhone to my agent?
Configure the remote MCP URL https://agent-phone-mcp.vercel.app/api/mcp as an SSE server in your MCP settings and add payment-signature if premium settlement applies.