Setting Up the Sendburg MCP Connector for Claude & ChatGPT
The Sendburg MCP connector lets Claude and ChatGPT search our contact database, check buying signals, and verify emails directly inside a conversation. Setup takes about two minutes per assistant. Here is the exact procedure, the prompts that work best, and the limits to know about.
What you get once connected
With the Sendburg MCP connector active, your AI assistant can search 150M+ verified contacts, look up company intelligence, check buying signals, and verify emails — all from plain-English requests inside the chat. No tab-switching, no CSV shuffling, no filter-clicking.
Connecting to Claude
- Open Claude (web or desktop) → Settings → Connectors
- Click Add custom connector and paste the Sendburg MCP server URL from your Sendburg dashboard (Settings → Integrations → MCP)
- Authorize with your Sendburg account when prompted — the OAuth flow takes one click
- Start a new conversation. Claude now lists Sendburg tools and will use them automatically when a request involves contacts or companies
Connecting to ChatGPT
- ChatGPT (paid plans) → Settings → Connectors
- Add the same Sendburg MCP server URL and complete the authorization
- Enable the connector for the conversation — ChatGPT confirms which tools it can call
Prompts that work well
- “Find 25 VPs of Sales at US SaaS companies between 50 and 200 employees that use Salesforce”
- “Which of these companies showed hiring or funding signals in the last 30 days?”
- “Verify these emails and flag anything risky before I export”
- “Brief me on the top five accounts — recent news, tech stack, and who else we should contact there”
How credits and limits work
MCP queries draw from the same credit pool as the web app — a contact reveal costs one credit whether it happens in the dashboard or in a chat. The free plan includes enough monthly credits to run real workflows; rate limits apply per minute to keep bulk jobs in the platform where they belong. For high-volume automation, use the REST API instead of chat.
Troubleshooting
- Connector not appearing: re-check the server URL and re-authorize; corporate SSO sessions occasionally need a fresh login
- Assistant answers from memory instead of querying: ask it explicitly to “use the Sendburg connector” once — it learns the pattern for the rest of the session
- Empty results: your filters may be over-constrained; widen one dimension at a time, exactly as you would in the app
Full background on why this workflow beats manual filtering: AI Prospecting in 2026.