Connect Campfire SMS as a local MCP server in Claude Code. Your agent can text task updates and retrieve your replies while it keeps working in its current repository.
Your agent
SMS OUTThe migration has two approaches. Keep the existing schema?
SMS INKeep it. Add the compatibility layer instead.
RESULTCompatibility layer added. Ready for you to review.
Your phone
Campfire SMS: The migration has two approaches. Keep the existing schema?
You: Keep it. Add the compatibility layer instead.
Campfire SMS: Compatibility layer added. Ready for you to review.
Keep your Claude Code environment
Your local tools, repository instructions, and project context are already useful. Campfire SMS adds phone contact to that setup. You do not move the code into a Campfire SMS workspace or build a new messaging bot.
Create an account, verify your phone, and install the connector on the computer running Claude Code. The agent remains responsible for the code and tools. Campfire SMS handles the SMS connection.
Register the local connector with Claude Code
You need a verified Campfire SMS account, Node.js 18+, Python 3.12+, and the computer where your agent already works. Start with local-agent setup. Copy the one-time command from your account:
npx -y @campfiresms/setup YOUR_INSTALLATION_CODE
YOUR_INSTALLATION_CODE is a placeholder. Your actual command is single use and expires after ten minutes. Setup saves the device credential in your user profile; you do not need to put it in your repository.
For Claude Code, register the local STDIO command printed by setup. This example uses python; replace it with the exact Python executable setup used, including an absolute virtual-environment path on Linux:
claude mcp add --transport stdio --scope user campfire -- python -m campfire_mcp.cli serve
claude mcp list
User scope makes this connection available across your repositories without adding a project configuration file. Restart Claude Code and use /mcp to inspect it. See Anthropic's MCP setup documentation for client configuration.
On Linux or a VM, follow the virtual-environment instructions before installing. Run setup as the same user who runs the agent.

Check both directions in the same session
Complete the account's test-message flow, then ask Claude Code to open a bridge and text you a small question. Reply with a harmless instruction, such as “summarize the current task.” Have the agent check for the reply, handle it, acknowledge the message, and text a confirmation.
The MCP server appearing in claude mcp list is a configuration check. The text-and-reply exercise checks the actual workflow you will use away from the computer.
Use SMS for the moments that need you
Work on the migration in this repo. Text me through Campfire SMS if you need a design choice, find a blocker, or finish the agreed work. Check for my replies while active, acknowledge handled messages, and keep summaries short. Preserve the existing scope and native permission checks.
A concise question travels well: “keep the schema or change it?” A large diff does not. Ask Claude Code to leave detailed evidence in the workspace and send only the result and next decision by SMS.
Keep the computer awake and online with Claude Code running and checking messages. For a full browser or mobile session view, compare Claude Code Remote Control and SMS.
Common questions
Does setup register Claude Code automatically?
The installer registers detected Codex and Grok Build CLIs. For Claude Code, add the local STDIO MCP command printed by setup and restart the client.
Is this the same as Claude Code Remote Control?
No. Anthropic's Remote Control offers access through its web and mobile interfaces. Campfire SMS provides short updates and replies through SMS; you can choose the interface that suits the task.
Will a text wake a stopped Claude Code process?
No. The local runtime must remain available and check the message queue. Campfire SMS does not restart a stopped local session.