# Give Claude Code a real phone number

> Install the Phonekit skill and Claude Code can read the texted code in your own app's sign-in and finish the step itself.

Claude Code gets a Phonekit number it can read. It triggers your app's sign-in text, reads the code and keeps going without asking you.

## Install the skill

```bash title="Install for Claude Code"
npx skills add https://www.phonekit.io --skill phonekit --agent claude-code --copy
```

Run it from the repository you open in Claude Code. Start a new session and type `/phonekit`. Add `--global` to install it for every project. [Claude Code's skills guide](https://code.claude.com/docs/en/skills) covers project, personal and account skills.

## Connect

### MCP

```bash title="Add Phonekit to Claude Code"
claude mcp add --transport http --scope user phonekit https://www.phonekit.io/api/mcp
```

In Claude Code, run `/mcp`, select Phonekit and authenticate. Phonekit's approval screen opens in your browser; choose the workspace, actions and lines for this connection. Claude Code stores and refreshes the token. See [Claude Code's MCP guide](https://code.claude.com/docs/en/mcp) and [Phonekit's MCP reference](https://www.phonekit.io/docs/mcp).

### CLI

Or ask Claude Code to connect Phonekit through the terminal. It runs the login and hands you the approval link. The CLI needs Node.js 20.3 or newer.

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

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

**Add a real sign-in test**

```text
Use /phonekit to finish our staging sign-in test. Read the existing Playwright test and the app's selectors first. Use the assigned QA number: mark it before clicking Send code, wait up to 120 seconds for the new code with the Phonekit SDK, enter it and assert the signed-in account page. Run the test and report the change and its final assertion. Keep the code out of your report.
```

**What done looks like**

A changed test that uses your app's own selectors, a 120-second deadline, a final signed-in assertion and a passing run. A code on its own is only halfway.

Set up the [SDK](https://www.phonekit.io/docs/sdk) first. Give each parallel run its own number, as [one number per test](https://www.phonekit.io/learn/one-number-per-test) explains.

## Cloud sessions and permissions

Skills enabled in your Claude account can sync into supported Claude Code sessions. A skill installed only in this repository stays with this repository, so commit it if a cloud session should use it. That session also needs its own Phonekit connection.

Claude Code's tool permissions decide which commands run without asking. They never approve number access; a person does that in Phonekit.

## Questions

### Does installing the skill also add the MCP server?

No. The skill is instructions. Add the MCP server with claude mcp add, or connect the CLI. Either way you approve the connection in Phonekit.

### Can Claude Code read every number in my workspace?

No. It reads only the lines you select when you approve the connection. Revoke the connection in Phonekit and access stops.

### Why can a cloud session not find the skill?

A skill installed on your machine does not reach a cloud session. Commit the project skill or enable it in your Claude account, and give that session its own Phonekit connection.

### 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/claude
