Source and reveal candidates from inside Claude with our MCP connector, or pull your contacts, companies and jobs into any tool with our REST API. No scraping, no CSV round-trips.
Pick the one that fits how you work. Both use the same account and the same credits — nothing new to learn about billing.
Connect ContactSearch to Claude (web, desktop, or Claude Code) and source candidates by chatting in plain English. Best for recruiters who want an AI assistant to do the searching, revealing and ATS work for them.
A simple REST API to pull your contacts, companies and jobs into n8n, Make, Zapier, a spreadsheet, or your own software. Best for teams who want ContactSearch data flowing into systems they already run.
If you live in Claude and want a hands-off sourcing assistant, start with MCP. If you have a developer or an automation tool that needs the raw data, use the API. You can use both.
MCP (Model Context Protocol) is the standard way to give an AI assistant access to an outside service. Connect once and Claude — or ChatGPT — can search, preview, reveal and push contacts to your ATS, all from a normal chat.
"Find Directors of Nursing hiring near Chicago." Claude parses it, previews matches and gives you a count — free.
Reveal work emails and mobile numbers on your say-so, and skip anyone you already own or have excluded.
"Who's hiring RNs this month?" Surfaces companies posting jobs, then the decision-makers to reach.
Send the new contacts straight into your ATS or CRM, tagged and on the right list.
Pull a contact's full work history, skills and a generated resume PDF without leaving the chat.
Claude checks your balance and always asks before spending a single credit.
Previewing candidates costs 0 credits. Credits are only used when you reveal contacts or run a premium mobile lookup — and Claude confirms with you first, every time.
The server endpoint is the same everywhere:
https://contactsearch.ai/api/mcp
https://contactsearch.ai/api/mcp and click Connect.Add this to your claude_desktop_config.json (Settings → Developer → Edit config), then restart Claude Desktop. Replace the key with your own from Settings → Integrations.
{
"mcpServers": {
"contactsearch": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://contactsearch.ai/api/mcp",
"--header", "Authorization:Bearer cs_live_YOUR_KEY_HERE"
]
}
}
}
claude mcp add --transport http contactsearch \
https://contactsearch.ai/api/mcp \
--header "Authorization: Bearer cs_live_YOUR_KEY_HERE"
On claude.ai web you sign in — no key to copy or paste. On Desktop and Claude Code you use an API key in the header. Same account either way.
Needs a paid ChatGPT plan, on the web. Tip: sign in to ContactSearch in another tab first, so the sign-in step is instant.
https://contactsearch.ai/api/mcp, Authentication OAuth, and upload the logo (download).ChatGPT's Developer-Mode connectors are newer and the menus move around; if a name doesn't match, look for Apps, Connectors, or Advanced settings. Claude's connector is the more polished path today.
A clean, read-only REST API for your contacts, companies and jobs. Point any HTTP tool at it — n8n, Make, Zapier, a Google Sheet script, or your own code — and pull data on your own schedule.
Bearer token.Send your key in the Authorization header:
curl -H "Authorization: Bearer cs_live_YOUR_KEY_HERE" \
"https://contactsearch.ai/api/v1/contacts?state=IL&per_page=25"
company, title, city, state. Paginate with page & per_page.q.company, since (YYYY-MM-DD). Newest first.application/pdf.{
"contacts": [ { "id": 12345, "name": "Sarah J.", "title": "Director of Nursing", ... } ],
"page": 1,
"per_page": 50,
"total": 1247,
"has_more": true
}
Anyone with your API key can read your whole contact database. Treat it like a password, send it in the header (not the URL), and revoke unused keys in Settings.
Want every parameter, error code and best practice? See the full technical reference:
One key works for both the API and Claude Desktop / Claude Code. (On claude.ai web you just sign in — no key needed.)
cs_live_a1b2c3d4…. Copy it now — it's only shown once.Registration is free and approval takes under 24 hours. Create an account →
No. Connecting is free, and so is previewing candidates and searching. Credits are only used when you reveal a contact's email/phone or run a premium mobile lookup — and with MCP, Claude always asks before spending them.
Yes. On claude.ai web you sign in through a secure window — your password and API key are never shared with Claude. Every request is scoped to your account only; you can never see or touch another company's data.
Absolutely. Many teams let recruiters source through Claude while their automation tools pull the resulting contacts via the API. Same account, same credits.
Any MCP-compatible client: Claude on the web (claude.ai), Claude Desktop, and Claude Code. More clients are adding MCP support over time.
Today, yes — it's for pulling your contacts, companies, jobs and resumes into your own tools. Sourcing, revealing and pushing to your ATS are done in the app or through the MCP connector.
Of course. Email support@contactsearch.ai and we'll walk you through connecting Claude or wiring up the API.