MCP connect
disburse ships a Model Context Protocol
server, so agents can use search, enrich, and verify as native tools; the
same engine as the REST API, exposed as tool calls.
The server lives at /mcp on the same host as the API and is bearer-authenticated
with the same API keys.
Available tools
| Tool | What it does |
|---|---|
search_people | Find people by natural-language query or filters |
search_companies | Find companies by natural-language query or filters |
enrich_person | Enrich a person by email: a profile merged across every source, with provenance and verification |
enrich_company | Firmographics and signals for a company domain |
verify_email | Validate an email (syntax, disposable, live MX) |
verify_phone | Validate a phone number |
Connect with an API key
Point any MCP client at the Streamable HTTP endpoint and pass your key as a bearer token. For Claude Desktop / Code, add it to your MCP config:
{
"mcpServers": {
"disburse": {
"url": "https://api.disburse.dev/mcp",
"headers": { "Authorization": "Bearer sk_live_your_key" }
}
}
}One-click connect (OAuth)
When the server is deployed with OAuth enabled, clients like Claude can connect with a single "Connect" click instead of a pasted key: you sign in, approve the scopes on the consent screen, and the client is issued a token that maps to your organization. No key handling on the client side.
Both paths authenticate against the same accounts: an API key and an OAuth session resolve to the same org and the same rate limits.