MCP server (Claude, ChatGPT and other AI assistants)

ReadyBuyerFinder has an MCP server, so an AI assistant can read your pipeline and act on leads when you ask it to.

URL: https://<your ReadyBuyerFinder>/api/mcp (for the hosted product, https://readybuyerfinder.com/api/mcp)
Transport: Streamable HTTP, stateless JSON-RPC over POST. No SSE stream. Protocol version 2025-06-18.
Auth: Authorization: Bearer sd_live_..., a workspace API key from Settings → API keys. The assistant sees only that workspace.

Tools

Tool	What it does
`ask_pipeline`	Answers a plain-English question about your leads (see Ask your pipeline)
`search_leads`	Lists leads by signal types, days, minimum score, status, country, city
`get_lead`	One lead: score breakdown, why-now signals, draft and fact-check result
`recent_signals`	Recent relevant signals, newest first
`approve_lead`	Approves a lead. It is pushed to the agent's destinations, the same as clicking Approve
`skip_lead`	Skips a lead so it leaves the inbox

Nothing in the MCP server sends email itself. Approving a lead pushes it to your sequencer or CRM, which then works as usual.

Connect Claude Desktop

Claude Desktop connects to remote servers with a header through the mcp-remote bridge. Add this to claude_desktop_config.json and restart Claude:

{
  "mcpServers": {
    "readybuyerfinder": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://<your ReadyBuyerFinder>/api/mcp", "--header", "Authorization: Bearer sd_live_YOUR_KEY"]
    }
  }
}

If your Claude app or claude.ai plan lets you add a custom connector with a request header, use the URL above and the header Authorization: Bearer sd_live_YOUR_KEY. ReadyBuyerFinder does not offer OAuth sign-in for connectors yet.

Connect Claude Code

claude mcp add --transport http readybuyerfinder https://<your ReadyBuyerFinder>/api/mcp --header "Authorization: Bearer sd_live_YOUR_KEY"

Test with curl

curl -s https://readybuyerfinder.com/api/mcp \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

curl -s https://readybuyerfinder.com/api/mcp \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

curl -s https://readybuyerfinder.com/api/mcp \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"ask_pipeline","arguments":{"question":"leads that raised money this month"}}}'

A wrong or missing key returns 401 with JSON-RPC error -32001.

Safety

Treat the API key like a password. The assistant can approve leads, so tell it to approve only when you ask. Delete the key in Settings to cut access at once.