AI coding agents like Claude Code, Cursor, and Windsurf can now write and run entire signup/verification flows on their own — except for the part where a real SMS/OTP code has to land somewhere. Model Context Protocol (MCP) closes that gap: it lets an agent call an external tool directly, mid-task, instead of a human copying a code back and forth.
What the sms-florin MCP server does
It wraps the same sms-florin API the website and npm SDK use, exposed as four MCP tools: list_services, rent_number, get_rental, and wait_for_sms. An agent testing a WhatsApp or Google signup flow can rent a real UK number and block on wait_for_sms until the code arrives, then keep going — no human in the loop.
Because the numbers are real SIM cards on EE/Three networks rather than VoIP, they pass the same carrier checks a human tester's number would.
Setup
Add it with one command:
claude mcp add sms-florin -e SMS_FLORIN_API_KEY=your_key -- npx -y sms-florin-mcp
It also works with any other MCP-compatible client (Cursor, Windsurf, Cline) — same npx command, same API key from /api-access.
Bottom line
If you're already using sms-florin's REST API or npm SDK for CI/QA automation, the MCP server is the same capability made available directly to an AI agent's own tool-calling loop, without writing glue code.
Originally published on flo-voice1.com.
Top comments (0)