# Give Cursor a real phone number

> Install the Phonekit skill and Cursor Agent can read the texted code in your own app, so it can reproduce and fix sign-in problems end to end.

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

```bash title="Install for Cursor"
npx skills add https://www.phonekit.io --skill phonekit --agent cursor --copy
```

Run 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](https://cursor.com/docs/skills) cover discovery.

## Connect

### MCP

Merge this entry into the project's `.cursor/mcp.json`, keeping any servers already there:

```json title="Project MCP configuration"
{
  "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](https://cursor.com/docs/mcp) and [Phonekit's MCP reference](https://www.phonekit.io/docs/mcp).

### CLI

The CLI runs in Agent's terminal and needs Node.js 20.3 or newer.

```bash title="Connect the Phonekit CLI"
npx phonekit@latest docs agents
npx phonekit@latest login --wait 50
npx phonekit@latest number list
```

Open 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](https://www.phonekit.io/docs/quickstart).

## Give it a task

**Reproduce and fix a sign-in bug**

```text
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](https://www.phonekit.io/learn/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.

---

Source: https://www.phonekit.io/integrations/cursor
