- Integrations
- Cursor
Give Cursor a real phone number
Cursor Agent gets a Phonekit number it can read. It can walk through your app's phone sign-in, find where it breaks and prove the fix.
Install the skill
npx skills add https://www.phonekit.io --skill phonekit --agent cursor --copyRun it in the project open in Cursor. The skill lands in .agents/skills, which Cursor reads. Start a new Agent chat, check Customize → Skills, then type /phonekit. Cursor's skills docs cover discovery.
Connect
MCP
Merge this entry into the project's .cursor/mcp.json, keeping any servers already there:
{
"mcpServers": {
"phonekit": {
"url": "https://www.phonekit.io/api/mcp"
}
}
}Open Customize → MCP, authenticate Phonekit and approve the workspace, actions and lines in your browser. Cursor handles the sign-in, so no key goes in the JSON. See Cursor's MCP guide and Phonekit's MCP reference.
CLI
The CLI runs in Agent's terminal and needs Node.js 20.3 or newer.
npx phonekit@latest docs agents
npx phonekit@latest login --wait 50
npx phonekit@latest number listOpen the approval link, check the short code and select the numbers this connection may read. Exit code 8 means approval is still pending; run login again to resume. The skill uses MCP when it's connected and the CLI otherwise. Name the number for your project with the quickstart.
Give it a task
Use /phonekit with the assigned staging number to reproduce the reported sign-in bug. Read the app and the existing test selectors first. Mark the number before sending, wait up to 120 seconds for the new code and finish the sign-in in the browser. Report the step that fails and what the app shows. If you change code, run the same journey again and show the signed-in assertion. Keep the code out of your report.
What done looks like
Before: the step that failed · Change: the fix in your app or test · After: the same journey reaching the signed-in page
Give each parallel run its own number, as one number per test explains.
Cloud Agents
A project skill travels with the repository. Personal skills in ~/.cursor/skills reach Cloud Agents only through Cursor's Cloud Agents sync setting; other local folders aren't copied. A Cloud Agent also needs its own Node runtime, access to your app and a Phonekit credential in its secrets.
Questions
Why doesn't Customize show Phonekit?
Check that SKILL.md is in the project's .agents/skills/phonekit directory and that Cursor has that repository open. Confirm the skill appears in Customize before chasing a CLI or delivery error.
Does personal skill sync also copy my Phonekit login?
No. Sync copies instructions. Give the Cloud Agent its own Phonekit credential and number in its runtime.
How do I turn a good Agent run into lasting coverage?
Ask Agent to put the SDK receiving step and the final assertion into your test suite, then run it in CI with a key scoped to its own number.
Which number type should I use?
Standard, a US local VoIP number, covers most tests of your own app. Use Mobile, a real SIM line on a mobile network, when a service you depend on only texts mobile numbers. No number is accepted by every service.
Keep reading
- Connect and name a numberConnect the Phonekit CLI, choose an authorized company number, and wait for a fresh SMS verification code.
- Use the SDK in your testInstall Phonekit's server-side SDK, capture message cursors, wait for OTPs, and handle deadlines and cancellation in JavaScript or TypeScript.
- Write the task for your agentGive Claude Code, Codex, Cursor and OpenCode a real US phone number, including real SIM lines, so they can sign in to your own app, read the code and text your product without asking you.
- Playwright sign-in testA complete Playwright SMS test: receive a fresh code with the Phonekit SDK, submit it in the browser, and assert the signed-in account.