Reveal verified emails, enrich companies, and check your credit balance without leaving Claude, ChatGPT, Gemini, or Cursor. No new tabs, no copy-pasting between tools — your assistant does the lookup for you.
For the full technical setup — endpoints, per-client configs, and troubleshooting — see the MCP documentation.
What is the SalesQL MCP?
MCP (Model Context Protocol) is the standard AI assistants use to connect to outside tools. In practice, it's a bridge between your SalesQL data and the chat window you're already working in.
Once connected, your assistant can:
Reveal a contact's work email, phone, job title, and LinkedIn
Enrich a full company profile (industry, size, location, LinkedIn)
Process up to 100 people or companies in a single pass
Check your credit balance and next refresh date
Resolve exact filter values before a search
This runs on the same account and the same credit balance you already use in the extension, dashboard, and API. It's not a separate product — it's another door into the same data.
Where it works
The server lives at a single endpoint (https://mcp.salesql.com/mcp, over Streamable HTTP) and connects today from:
Claude Desktop and Claude Code
ChatGPT (Developer Mode)
Gemini CLI
Cursor
Perplexity (Connectors)
VS Code (GitHub Copilot, agent mode)
Any client that speaks Streamable HTTP
Every client points at the same endpoint — only where you paste the key changes. Exact steps for each, with ready-to-copy config blocks, are in the MCP documentation.
Before you start
You'll need an active API/MCP key, generated from your dashboard under Enrichment API. For security, don't share it in a chat message — each client has its own local place to store it.
Connecting in 3 steps
Pick your client. Claude Desktop and Claude Code are the fastest paths if you already work inside the Claude ecosystem; Cursor and VS Code fit better if you live in your editor.
Paste the config. Each client uses a different file or screen (
claude_desktop_config.json,~/.cursor/mcp.json, ChatGPT's connector panel, etc.), but the structure is always the same: the MCP endpoint plus your key as a Bearer token.Restart the client. Most assistants need a full restart to read the new config and show SalesQL's tools in the composer.
If you'd rather have your assistant build the config file for you, the documentation includes a ready-to-paste prompt for each client — it walks you through setup without asking you to expose your key in the conversation.
What you can ask your assistant
Once connected, there's nothing to memorize — plain language works:
"Enrich linkedin.com/in/jane-doe and draft a short intro email in my voice."
"Find the direct dial and verified email for Acme's VP of Marketing."
"Enrich these 40 LinkedIn URLs with verified emails and export as CSV."
"Give me the size, industry, and key decision-makers at acme.com."
"Who is behind [email protected]? Give me their full name, title, company and LinkedIn."
"How many enrichment credits do I have left this month, and when do they refresh?"
Bulk requests work the same way: paste up to 100 LinkedIn URLs, emails, or names and ask for a CSV back. One bulk call runs under the hood — you keep the conversation, and only the profiles that actually match spend credits.
Built for developers too
The MCP isn't limited to chat assistants. Cursor, VS Code, and any MCP-ready agent get the same tools — enrichment inside coding sessions, automations, or internal apps, drawing on your existing credit balance. A common pattern: "Before I email this list, verify which addresses are still valid," run straight from your IDE while you keep working.
Credits and limits
The MCP and the REST API draw on one shared credit balance and one shared rate limit, no matter how many keys or clients you have connected. Each successfully enriched contact or company costs 1 credit; a search with no match doesn't. Checking your account or resolving filters (get_account_status, lookup) is always free.
Go over your plan's per-minute limit and you'll get a 429 — back off for a few seconds and retry.
What's live, and what's next
MCP keys carry scopes that gate what they can do:
account(read) — usage, plan, and credit balance. Live.enrich— reveal and enrich people & organizations, single and bulk. Live.search(read) — Prospector, search people & companies. Coming soon.verify— email verification. Coming soon.campaigns(read/write/send) — create and manage outbound campaigns. Later.
Today's keys grant full access to what's live. If your assistant can't run a Prospector search or verify an email yet, that's expected — not a bug.
Common issues
The client won't connect. Confirm the transport is Streamable HTTP and the URL ends in /mcp. The most common cause is a missing or mistyped Bearer key.
"Insufficient credits." Check your balance with the account status tool and top up from the dashboard if needed.
A search returns no match. No credit is charged. Try the contact's LinkedIn URL — it's the most reliable identifier.
Claude Desktop won't connect or throws npm errors. Usually an outdated Node version. The full documentation walks through checking and fixing it step by step.
For every other client-specific error — including Claude Desktop and Claude Code edge cases — the technical guide at salesql.com/docs/mcp has the full detail, with exact config blocks to copy.
FAQ
What is the SalesQL MCP? A server that connects SalesQL's verified contact data to AI tools via the Model Context Protocol. Your assistant gets tools like enrich_person and calls them when you ask.
Which AI tools work with it? Claude Desktop, Claude Code, ChatGPT (Developer Mode), Gemini CLI, Cursor, Perplexity, VS Code, and any other client that speaks Streamable HTTP.
Do I need to be a developer? No. Connecting from Claude Desktop, ChatGPT, or Perplexity is a config-paste-and-restart process — no code involved. Cursor and VS Code are aimed at developers, but the setup itself is the same three steps.
What does it cost? Nothing on top of your plan. The MCP uses the same credits you already have; there's no separate MCP fee. get_account_status and lookup are always free.
Is my data safe? The MCP runs on your existing SalesQL account and is GDPR-aligned, sharing the same credit balance and permissions model as the API. See our Privacy Policy and Data Processing Addendum for details.
For a broader look at what the MCP does, see the product overview.