AgentPhone Apex
Let coding agents place or manage voice and SMS outreach through one MCP gateway instead of custom telephony SDK glue.
Overview
AgentPhone is a MCP server for the Build phase that provides a multi-channel voice and SMS gateway interface for AI communication.
What is this MCP server?
- 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
- One documented remote SSE URL
- Two communication modalities stated: voice and SMS
What problem does it solve?
Hooking agents to real phone and SMS channels usually means juggling multiple carrier APIs and one-off scripts.
Who is it for?
Solo builders 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 do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
How it compares
Telephony MCP gateway, not a marketing automation skill or local CLI dialer.
Common Questions / FAQ
Who is AgentPhone for?
Indie 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.