Receive company SMS with Claude Code and Claude
Let Claude Code finish an SMS step while building or testing your app. For Claude chat and Cowork, choose the connection route that supplies tools to that execution surface.
Install the Phonekit skill
npx skills add https://www.phonekit.io --skill phonekit --agent claude-code --copyRun the install command from the repository you open in Claude Code. The skills installer selects Phonekit and copies it into Claude Code's project skill directory. You do not need to create folders or download the instruction file yourself.
Start a new Claude Code session and enter /phonekit. This invokes the installed skill. For use across projects, add --global to the install command. Claude Code's skills guide explains project, personal and account-synced skills.
Choose a Phonekit connection
Use the CLI route below, or an authenticated MCP connection if your Phonekit deployment supports it. Installing the skill does not set up both connections.
Connect through the CLI
For the local terminal route, ask Claude Code to connect Phonekit. It runs the login command and gives you the browser approval link. You approve the workspace and readable numbers; installing the skill does not grant inbox access. Node.js 20.3 or newer is required for the CLI.
npx phonekit@latest login --wait 50
npx phonekit@latest number listUse the quickstart to name the intended number. Exit code 8 means approval is still pending; repeat login to resume the same request.
Use Claude Code's MCP connection
For a Phonekit deployment with hosted connections enabled, add its endpoint using Claude Code's own MCP command:
claude mcp add --transport http --scope user phonekit https://www.phonekit.io/api/mcpIn your Claude Code session, run /mcp, select Phonekit and authenticate. The browser opens Phonekit's approval screen; choose the workspace, actions and lines for this connection. Confirm that /mcp shows the server connected. Claude Code owns token storage and refresh. Follow Claude Code's MCP instructions and Phonekit's MCP guide.
The skill uses an authenticated Phonekit MCP connection when available, otherwise the CLI. An MCP connection does not require a second CLI login. Use one connection for each workflow. The public hosted connection is awaiting deployment verification in Claude. Until that check is complete, use the CLI route.
Turn a manual signup check into a regression test
Use /phonekit to finish our staging signup test. Inspect the existing Playwright test and application selectors first. Use the assigned QA number, mark before clicking Send code, receive the fresh code within 120 seconds, enter it, and assert the authenticated account page. Implement the receiving step with the Phonekit JS/TS SDK. Run the test and report the changed test plus its final assertion; keep codes out of the report.
Completion evidence to ask for
Follow the SDK installation guide before implementing an SDK test.
A changed test using the application's own selectors, a receiving deadline, a final authenticated-state assertion, and a run result. A returned code alone is only an intermediate step.
Connect Claude chat or Cowork
On Claude Pro or Max, open Customize → Connectors → + Add → Add custom connector and enter the Phonekit deployment's /api/mcp URL. On Team or Enterprise, an authorized organization owner first adds the connector under Organization settings → Connectors → Add → Custom → Web; members then connect from Customize → Connectors. Authenticate through Phonekit and select the connection's permissions. Use the Claude custom connector guide. If Claude asks how to identify the OAuth client, choose Register automatically for Phonekit's implemented dynamic registration flow. This route needs a hosted endpoint reachable by Claude; a local project skill or terminal login does not supply that connection.
Skills enabled in your Claude account can sync into supported Claude Code and Cowork sessions. A skill installed only in this project's directory is for that project; personal machine files do not configure hosted sessions. Follow Claude's skills guide for account and cloud behavior.
Phonekit does not currently have a published Claude plugin marketplace listing. The skill installer above works independently of a listing. The public hosted connector is awaiting verification in Claude.
Questions you may have
Why can Claude Code find the skill but a cloud task cannot?
Commit the project skill for a cloud checkout, or use a skill enabled in the Claude account where the session runs. A personal machine installation does not configure a cloud worker. The runtime also needs its own Phonekit connection.
Can I approve every command automatically?
Use Claude Code’s tool permissions for the workflow you intend to run. The skill explains retrieval, but it does not approve Phonekit number access or authorize new account actions. A person reviews the connection in Phonekit.
Does Claude chat use the same credential as Claude Code?
Claude Code MCP and Claude chat connectors authenticate through their own host-managed connection. The CLI device login is separate. Give each connection a clear owner and select its scope deliberately.
Does installing the skill also install an MCP server?
The skill installs instructions. Add the MCP endpoint with claude mcp add and approve it separately, or use the CLI login. A Claude plugin can bundle both, but this installation does not depend on a published Phonekit plugin.