Why this matters
Claude Desktop ships native MCP support. Once you point it at ReachOut's MCP server, every tool — contacts, segments, campaigns, analytics — 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.
- Tools are scoped to the projects your API key is granted, so the agent only sees that data.
- Works with all of Claude's tool-calling features: streaming, image input, function calling.
Setup in 4 steps
- Generate a ReachOut API key.Open Studio → Organization settings → API keys → Generate API key, then grant it the editor role on your project. Copy the key. The key is scoped to your active organization.
- 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://api.usereachout.com/mcp with your bearer token.
- 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.
- 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://api.usereachout.com/mcp",
"transport": "http",
"headers": {
"Authorization": "Bearer YOUR_REACHOUT_API_KEY"
}
}
}
}