disburse / docs

Connect Claude

Disburse plugs into Claude as a connector: Claude gets search, enrich, and verify as native tools and calls them itself while you talk normally. Setup is a one-time, two-minute job, and no API key is needed for the main path: you sign in to your Disburse account once and Claude stays connected.

Custom connectors work on every Claude plan, including Free (Free allows one custom connector). On Team/Enterprise an owner adds Disburse once under Organization settings → Connectors, then each member clicks Connect.

Add Disburse to Claude (claude.ai)

  1. Open claude.ai and click your initials (bottom-left), then Settings.
  2. Go to Connectors (under Customize), click +, then Add custom connector; or jump straight to the dialog with this link.
  3. Fill in the dialog:
    • Name: Disburse
    • URL: https://api.disburse.dev/mcp
    • OAuth client: leave it on Register automatically. Claude detects that our server supports it and pre-selects it; nothing to set up.
  4. Click Add, then Connect. A Disburse sign-in window opens: log in with your Disburse account and click Approve on the consent screen.
  5. That's it. Back in claude.ai the connector shows as Connected.

Turn it on in a chat

  1. Start a new chat and click + under the message box, then Connectors.
  2. Make sure Disburse is toggled on. It stays on for future chats.

Try it

Ask in plain words; Claude picks the right tool on its own:

  • "Find fintech CFOs in Sydney with verified emails"
  • "Get me 100 founders in Australia as a list" — one call; the server builds, deduplicates, and quality-labels the whole list
  • "Export 2,000 marketing directors to a CSV" — Claude starts a server-side export and hands you the file
  • "Enrich sarah@acme.com"

Claude Desktop and Claude Code

Claude Desktop uses the same connector: it is added under Settings → Connectors exactly as above, and a connector added on claude.ai is already there. The desktop config file only holds local servers, so it is not the place for Disburse.

Claude Code and other MCP clients take the URL directly. If you prefer an API key (sk_live_… from your dashboard) over the sign-in flow, add this to the client's MCP config (VS Code, Windsurf and Codex name these fields differently; MCP connect has a block for each):

json
{
  "mcpServers": {
    "disburse": {
      "type": "http",
      "url": "https://api.disburse.dev/mcp",
      "headers": { "Authorization": "Bearer sk_live_your_key" }
    }
  }
}

For Claude Code it's one command, then /mcp inside a session to sign in:

bash
claude mcp add disburse --transport http https://api.disburse.dev/mcp

Prefer a key over the sign-in? Add it as a header instead:

bash
claude mcp add disburse --transport http https://api.disburse.dev/mcp \
  --header "Authorization: Bearer sk_live_your_key"

Both paths land on the same account and the same rate limits; the MCP connect page covers the tools and options in depth.

Troubleshooting

  • Claude says it doesn't have a Disburse tool: the connector is added but toggled off for that chat — click + under the message box, then Connectors, and toggle Disburse on.
  • Tools look stale after we ship new ones: open Settings → Connectors and use the connector's ⋯ menu → refresh/reconnect to pull the latest tool list.
  • Connect button loops or fails: log in at app.disburse.dev first, then retry Connect.
  • "Permission required" prompts: Disburse tools are declared read-only, so Claude normally calls them without asking. If prompted anyway, choose Always allow.