TL;DR: Add https://mcp.cleanlist.ai/v1/mcp as a custom connector in Claude and sign in with your Cleanlist account. No Client ID, API key, or install. Claude can then search people and companies, build lead lists, enrich contacts, and push leads to your CRM, using your workspace's data and credits. Available on Pro and Scale (and AppSumo tiers 5-7).
Cleanlist MCP connector for Claude
The Cleanlist connector lets Claude work in your Cleanlist workspace from a conversation. Ask in plain language ("find VPs of Sales at fintech companies in New York and save them to a list"), and Claude calls Cleanlist's tools to do it. It uses the Model Context Protocol (MCP) (opens in a new tab), so it also works with other MCP clients that support remote servers with OAuth.
The connector acts as you, in one Cleanlist workspace. It sees the same lists and credits you see in the portal, and it can only do what your account can do there.
Requirements
- A Cleanlist account with a finished workspace (complete onboarding in the portal (opens in a new tab) first)
- A plan that includes the public API and MCP: Pro or Scale, or AppSumo tiers 5-7. See What's Included by Plan
- A Claude plan that supports custom connectors
Connect in Claude
Add a custom connector
In Claude, open Settings, then Connectors, and click Add custom connector. This works the same in claude.ai and the Claude desktop app, and the connector then appears in the mobile app and Cowork too.
Enter the Cleanlist URL
Name it Cleanlist and paste:
https://mcp.cleanlist.ai/v1/mcpLeave Authentication on Sign in now and OAuth client on Use Claude's published identity. Claude detects both from the server, so there's no Client ID to enter. Click Add.
Sign in and approve
Click Connect. Sign in with your Cleanlist account if you aren't already, pick the workspace, and review what Claude is asking to access: your identity, basic profile, email address, public metadata, and organization membership. Click Allow.
Use it in a conversation
Back in Claude, Cleanlist's tools are available in any conversation. Turn the connector on or off per conversation from the tools menu.
More than one workspace? Add one connector per workspace. In the Cleanlist portal (opens in a new tab), switch to the workspace, open Integrations, then Connect to Claude, and copy the URL shown there. It ends in ?org=…, so that connector always acts in that workspace.
What Claude can do: tool groups
Tools come in groups. A connector gets the default groups unless its URL asks for others. To get every group, use https://mcp.cleanlist.ai/v1/mcp?tools=all. To pick groups, list them: ?tools=agents,crm. Workspace basics are always included.
| Group | Included | What it covers |
|---|---|---|
Workspace basics (core) | Always | Show connected account, check credits, estimate cost, get lists, get integrations, look up filter values, read workflow guide, read task results |
Prospecting (prospecting) | Default | Search people, search companies, find similar companies, preview a people search |
Lists (lists) | Default | Create, rename, and delete lists; add, remove, move, list, and filter leads; manage folders |
Enrichment (enrich) | Default | Enrich a person, a company, found people, found companies, or a whole list; check or cancel an enrichment; find personal emails |
Agents (agents) | ?tools=agents | Qualify leads against your ideal customer profile, research leads, run smart agents, create and update custom agents, read agent results |
CRM and sequencer (crm) | ?tools=crm | Check CRM status and records, preview a CRM push, push leads to HubSpot or Salesforce, add leads to a Lemlist campaign |
Export (export) | ?tools=export | Export a list as CSV, get leads as JSON |
Admin (admin) | ?tools=admin | List API keys, get a usage report |
Each tool tells Claude whether it only reads, changes data, or deletes it. Claude can run read-only tools, such as searches, without asking each time, and always asks before a tool that deletes data or writes to an outside system such as your CRM. AppSumo workspaces see a smaller set of tools.
Credits and approvals
- Searching is free. People and company searches don't spend credits.
- Paid actions are quoted first. Before enrichment, agents, or other paid work, the connector gets a cost estimate for the exact selection. Claude shows you the cost and runs it only after you approve.
- Credits come from the connected workspace, the same balance as the portal. Ask Claude "how many credits do I have?" at any time. Per-action prices are on the pricing page.
- Writes to other systems (pushing to a CRM or a Lemlist campaign) always ask for approval, and Claude can preview a push before making it.
Example prompts
1. Find people and save them to a list
Find VPs of Sales at US-based SaaS companies with 50-200 employees, and save the first 25 to a new list called "Q4 SaaS VPs".
Expected: if something material is missing (for example, which regions count), Claude asks one short follow-up. It then runs a free people search, shows the matches as a table with company links, creates the list, and saves the 25 people you picked.
2. Enrich a list
Enrich my "Q4 SaaS VPs" list with work emails.
Expected: Claude gets a cost estimate for that list and shows you the credit cost and your balance. After you approve, it starts the enrichment and reports progress until it's done, then summarizes how many contacts got emails.
3. Check the workspace
Which lead lists do I have, how many leads are in each, and how many credits do I have left?
Expected: Claude lists your lead lists with their lead counts and shows your current credit balance. Nothing is changed and no credits are spent.
4. Research and qualify leads (needs ?tools=agents)
Score the leads in "Q4 SaaS VPs" against my ideal customer profile and show me the top 10.
Expected: Claude first tells you what your ideal customer profile says, since every score is measured against it. It then quotes the per-lead cost and asks for approval, runs the qualification agent, and shows the highest-scoring leads with a fit score, a qualified or disqualified verdict, and the reasons for each.
Disconnect
To disconnect, open Settings, then Connectors in Claude, select Cleanlist, and remove it. Claude can no longer call Cleanlist after that. Your Cleanlist data and lists are unchanged.
Troubleshooting
| What you see | What to do |
|---|---|
| Connected, but no Cleanlist tools appear | Your workspace may not include MCP (see Requirements), or onboarding isn't finished. Finish setting up your workspace in the portal (opens in a new tab), then disconnect and connect again |
| A tool you expect isn't available | It's in a group your connector didn't ask for. Edit the connector URL to add ?tools=all, or the group name, and reconnect |
| The connector acts in the wrong workspace | Copy the workspace's own URL (with ?org=…) from Integrations, then Connect to Claude, and add it as a separate connector |
| Claude says you're out of credits | Top up or upgrade in the portal. Searching keeps working, because it's free |
Still stuck? Email support@cleanlist.ai.
Privacy and data
- The connector reaches your Cleanlist workspace through your own account, after you approve access. It can only see and change what your account can see and change in the portal.
- Cleanlist receives the inputs Claude sends to its tools (for example, search criteria or a list name), not your whole conversation.
- Your workspace data is handled as described in the Cleanlist privacy policy (opens in a new tab). Questions: privacy@cleanlist.ai.
Related
- MCP API reference (v2): the API the connector is built on
- What's Included by Plan
- Using Cleanlist Copilot: the in-app assistant