Model Context Protocol · Early access

Your AI agent can run outreach now.

The ReachOS MCP server exposes leads, lists, and campaigns as tools for Claude and any MCP client — so your agent researches, drafts, and queues cold outreach conversationally, while every deliverability guardrail stays enforced on our side.

One prompt, end to end

“Find my HVAC leads with verified emails, build a list, write a 3-email sequence about our maintenance plans, and show me everything before we send.”

The agent queries leads, saves the list, generates the sequence — and stops. Launching is a human decision, by design.

Seven tools. Honest annotations.

reachos_list_leadsread-onlyQuery your leads — by email presence, pipeline stage, or business name.

reachos_list_listsread-onlySee saved lead lists. Campaigns are always built from a list.

reachos_list_campaignsread-onlyList campaigns with statuses and generated email counts.

reachos_campaign_statsread-onlyOpen, click, and reply stats for any campaign.

reachos_create_listwriteSave a filtered set of leads as a reusable list.

reachos_create_campaignwriteGenerate the email sequence copy. Spends credits — sends nothing.

reachos_launch_campaigndestructiveEnqueues real cold email. Flagged destructive — conforming clients ask the human first.

Built for the part everyone worries about

The send tool admits it's dangerous

reachos_launch_campaign ships with destructiveHint: true, so conforming MCP clients prompt the human before real email moves — and its description instructs the model to confirm the campaign, lead count, and cadence first.

Guardrails live server-side

Tier limits, verified senders, warmup ramps, hourly caps, bounce auto-pause, unsubscribe lists, and spam scanning are enforced by ReachOS itself. None of it is reachable — or skippable — from the agent.

Launching enqueues. Humans and crons send.

Even an approved launch only queues sequences — ReachOS's own scheduler does the sending on its normal rules. An agent can never blast your list in one tool call.

Works where your agent lives

Standard MCP over stdio — register it with Claude Desktop, Claude Code, or any MCP-capable agent framework:

{
  "mcpServers": {
    "reachos": {
      "command": "node",
      "args": ["path/to/reachos-mcp/index.js"],
      "env": {
        "REACHOS_BASE_URL": "https://reachos.net",
        "REACHOS_SERVICE_KEY": "<your key>"
      }
    }
  }
}

Early access: service keys are provisioned per account by our team while we finish self-serve key management. Join the list below and we'll set you up.

Put your agent to work.

Early access is open — hosted keys, setup help, and a direct line to us.

Not using agents yet? ReachOS works great with just humans too.