English Français العربية

Campfire SMS

Official registry Developer tools

Hosted two-way SMS bridge: your coding agent texts you when it needs an answer; you reply by SMS.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http campfire-sms 'https://api.campfiresms.com/mcp' --header 'Authorization: <Per-installation bearer credential from your campfiresms.com account (sign up and verify your phone first). Use: Bearer <credential>. Requests without it get HTTP 401.>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "campfire-sms": {
            "type": "http",
            "url": "https://api.campfiresms.com/mcp",
            "headers": {
                "Authorization": "<Per-installation bearer credential from your campfiresms.com account (sign up and verify your phone first). Use: Bearer <credential>. Requests without it get HTTP 401.>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Campfire SMS MCP
  2. How it works
  3. Install (through campfiresms.com)
  4. Local agents
  5. Hosted MCP
  6. Tools
  7. Limits and safety
  8. Links
  9. About this repository

Campfire SMS MCP

Text your agent. Campfire SMS is a hosted two-way SMS bridge: your agent texts you when it needs an answer or has a result, and you reply by SMS from your normal text inbox.

Don't pip install this repo or use an npx package name without an installation code. Start at campfiresms.com.

How it works

  • Your agent opens a bridge and sends you a text when it needs input or finishes something.
  • You reply from your phone's normal text inbox. No phone app to install.
  • The agent retrieves your reply and keeps working with its own model, tools, and permissions. Campfire SMS handles phone enrollment, SMS delivery, the authenticated message queue, and routing.

Campfire SMS is not a service that gives an agent a phone number for other people to text. It connects your agent to you, the person running it.

Install (through campfiresms.com)

  1. Sign up at campfiresms.com.
  2. Verify your phone. You get 40 free messages, no card required.
  3. Copy the one-time install command from your account (Add computers → Add a computer or Bot → Create install command).

Full instructions: campfiresms.com/install.html

Local agents

For Codex, Claude Code, Grok Build, OpenCode, or another compatible MCP host on your computer. Run the command your account shows:

npx -y @campfiresms/setup YOUR_INSTALLATION_CODE
  • YOUR_INSTALLATION_CODE comes from your account. The command is single use and expires after 10 minutes; if it expires, create a new one.
  • Requires Node.js 18+ (with npx) and Python 3.12+.
  • Setup stores the installation credential locally and registers detected Codex and Grok Build CLIs. For other hosts, add a local MCP server named campfire using the command setup prints.
  • On Linux or a VM, run setup as the same non-root user as the agent, inside a Python virtual environment. Don't use sudo pip, system pip, or --break-system-packages. See the Linux/VM instructions.
  • Keep the computer awake and online with the agent session running. Campfire SMS does not wake a stopped local session.

To refresh a saved local connection: npx -y @campfiresms/setup update

Hosted MCP

Streamable HTTP endpoint:

https://api.campfiresms.com/mcp

It requires a per-installation bearer credential from your account, sent as Authorization: Bearer <credential>. It does not work without that credential: adding the URL alone (for example, through a directory's one-click install) gets HTTP 401.

To get the credential, run your account's install command with --credential-only (needs Node.js 18+, no Python or pip). Put the credential only in your client's secure credential settings.

Example for Grok Bot cloud routines: connect the hosted MCP with the credential, then set up an active webhook routine and save its URL and key under Grok Bot 24/7 wake in your account. An incoming text can then start the routine while your PC is off. See the Grok Bot walkthrough.

Tools

ToolPurpose
campfire_open_bridgeOpen (or reuse) an SMS bridge to your verified phone
campfire_send_messageSend you a text
campfire_check_messagesRetrieve your pending replies (they repeat until acknowledged)
campfire_ackAcknowledge message IDs after handling them
campfire_close_bridgeClose the bridge when the session is done

Limits and safety

  • SMS replies don't grant the agent new permissions. They can steer work within the agent's existing permissions; native approvals stay in the agent.
  • SMS is not end-to-end encrypted. Don't text passwords, credentials, payment details, or other secrets.
  • Each text sent or received counts as one message. Messaging pauses when your messages run out. See pricing.

About this repository

This repository holds the source of the earlier v0.1.1 Python connector, for reference. The current @campfiresms/setup installer bundles the maintained connector. For a new installation, use the steps above, not this source.

Frequently asked questions

What is Campfire SMS?

Hosted two-way SMS bridge: your coding agent texts you when it needs an answer; you reply by SMS.

How do I install Campfire SMS?

It runs as a remote server. In Claude Code: claude mcp add --transport http campfire-sms 'https://api.campfiresms.com/mcp' --header 'Authorization: <Per-installation bearer credential from your campfiresms.com account (sign up and verify your phone first). Use: Bearer <credential>. Requests without it get HTTP 401.>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Campfire SMS need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Campfire SMS open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Campfire SMS?

It is published by campfiresms. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.