ReachOut + Claude Desktop

Why this matters

Claude Desktop ships native MCP support. Once you point it at ReachOut's MCP server, every tool — contacts, segments, campaigns, analytics, audit log — becomes available as a typed function call inside any conversation. Marketers stop alt-tabbing between chat and dashboard; agents resolve segments, schedule sends, and read attribution without ever leaving the chat surface.

What you get

• Native MCP support — no glue code, no shim, no Zapier middleware.
• Per-user API keys; the active organization is implicit per token.
• Every tool call lands in ReachOut's tenant-wide audit log with the agent session ID.
• Approval gates available for high-volume sends so agents can't one-shot a 100k campaign.
• Works with all of Claude's tool-calling features: streaming, image input, function calling.

Setup in 4 steps

1. Generate a ReachOut API key. Open Studio → Settings → API keys → Create. Copy the key. The key is scoped to your active organization.
2. Edit the Claude Desktop config. On macOS, edit ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows, %APPDATA%\Claude\claude_desktop_config.json. Add an mcpServers entry pointing at https://reachout-pulse-api.usereachout.com/mcp with your bearer token.
3. Restart Claude Desktop. The MCP server appears in the tools menu within a few seconds. The first prompt that names ReachOut auto-discovers the tool surface.
4. Test with list_contacts. Ask Claude "list my ReachOut contacts." It calls list_contacts and surfaces the response with the [organization] header so you always know which tenant you're looking at.

Configuration

{
  "mcpServers": {
    "reachout": {
      "url": "https://reachout-pulse-api.usereachout.com/mcp",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer YOUR_REACHOUT_API_KEY"
      }
    }
  }
}