
PhoneMCP: AI Powered Texts
Send and receive SMS on your own phone through MCP so agents can capture OTPs and automate signup flows.
Overview
com.phone-mcp/phonemcp-mcp-server is a MCP server for the Build phase that sends and receives SMS on your phone for OTP and workflow automation via agents.
What is this MCP server?
- Send and receive texts via MCP using your own phone (PhoneMCP v0.1.1)
- SSE remote at https://phone-mcp.com/sse
- OTP retrieval for automating account signup and 2FA-heavy workflows
- Signup and pairing at phone-mcp.com before production use
- Agent-driven SMS automation without maintaining a separate Twilio sandbox for every experiment
- Server version 0.1.1
- Transport: SSE at phone-mcp.com/sse
- Requires phone-mcp.com signup for operational use
What problem does it solve?
Builders waste time manually copying OTPs from their phone while agents cannot complete signup or SMS-gated integration tests.
Who is it for?
Solo developers automating OTP-heavy signups, personal workflows, or agent demos that need real SMS on a phone they control.
Skip if: High-volume transactional email/SMS products, regulated healthcare messaging, or teams that cannot tie automation to a personal device.
What do I get? / Deliverables
Your agent can read and send texts through your paired phone so auth and SMS-dependent workflows run end-to-end without constant context switching.
- Inbound SMS/OTP text available to the agent during sessions
- Outbound texts triggered from agent tool calls where permitted
- Faster iteration on SMS-gated signup and integration tests
Recommended MCP Servers
Journey fit
SMS bridges belong in Build when you connect real-world verification and notification paths to the product you are shipping. Integrations covers PhoneMCP’s SSE remote that replaces brittle SMS gateways for personal-device automation.
How it compares
Personal-phone SMS MCP bridge, not Twilio-scale CPaaS or a voice-call telephony server.
Common Questions / FAQ
Who is com.phone-mcp/phonemcp-mcp-server for?
Indie builders and agent users who want MCP-driven SMS on their own phone for OTPs and small automation jobs during development.
When should I use com.phone-mcp/phonemcp-mcp-server?
Use it while building or testing features that depend on SMS verification, inbound codes, or short automated text sequences you are willing to run on your handset.
How do I add com.phone-mcp/phonemcp-mcp-server to my agent?
Sign up at phone-mcp.com, complete their phone pairing flow, then add the SSE MCP remote https://phone-mcp.com/sse in Claude Code, Cursor, or your MCP client.