Lusha MCP connector
The Lusha connector brings contacts, companies, buying signals and ICP fit scores into Claude, ChatGPT, Cursor and Microsoft Copilot, so anyone on the sales team can search, enrich and prioritize prospects without leaving their chat.
- Connects with an API key
- Free 14-day trial
- No credit card
Find VP Sales contacts at fintech companies with 200 to 500 staff
Working in Lusha with Elaichi
-
List all Lusha person
-
Get single Lusha contact enrich job by ID
-
Get single Lusha contact prospecting filter by ID
How to connect Lusha to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Lusha MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Lusha MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Lusha MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Lusha MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Lusha MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Lusha to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Lusha through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lusha is logged.
-
Sales
Fill in a contact before the first call
Ask for the direct dial, email and current title of a prospect, enriched from Lusha, before you pick up the phone.
-
Sales development
Build a prospect list from one description
Describe the title, industry, company size and location you want and get a list of matching Lusha contacts, already enriched.
-
Marketing
Find lookalikes of your best customers
Hand over a few accounts that closed and get Lusha companies that look like them, ready to drop into a campaign.
-
Revenue operations
Score an inbound list against your ICP
Paste in a batch of companies and get each one's ICP fit score and signal score so reps work the right ones first.
-
Sales
Map the buying group at a target account
Ask who else at a company is involved in the decision and get the Lusha buying group with their roles and contact details.
-
Customer success
Spot accounts showing intent this week
Check which target companies have visited your website or set off a signal in Lusha, and plan outreach around it.
Try asking
- “Find VP Sales contacts at fintech companies with 200 to 500 staff”
- “Enrich acme.com with phone, email and ICP fit score”
- “Which target accounts visited our website this week?”
What connecting Lusha gets you
6 screens from Elaichi, each doing one job for your Lusha account.
Ask Elaichi to work across your apps.
Find VP Sales contacts at fintech companies with 200 to 500 staff
Enrich acme.com with phone, email and ICP fit score
Which target accounts visited our website this week?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Lusha questions in plain words.
Get decision makers, direct dials and company details from live Lusha records in one message.
Copy the endpoint
AI apps
Lusha works in every client you use.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.
Tool catalog
68 Lusha tools, no code to write.
Contacts, companies, signals, scores and lookalikes, cataloged and ready without a line of custom code.
Toolboxes
Every team gets its own Lusha toolbox.
Sales prospects, marketing builds lookalike lists, and operations watches credits, each from a scoped toolbox.
Shared connections
Share Lusha access, never the API key.
One person connects Lusha, whole teams enrich contacts through it without seeing a credential.
Audit log
Every Lusha search and enrichment is logged.
See who enriched which contact, when, and from which client, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Lusha digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch contacts
Lusha
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Lusha
Queued
Workflows
A schedule starts prospecting, a person approves.
New Lusha signals are fetched, grouped, drafted into a digest, approved, then posted back.
Lusha health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Companies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales US 27%
Outbound 21%
Marketing 18%
Collections and dashboards
Lusha health, computed, not asked for.
Credits used, contacts enriched and signals by team, counted on a schedule with no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Lusha
All three can connect Lusha to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Lusha tools | Allow or restrict single Lusha tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Lusha call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Lusha tools for your AI agents
68 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lusha, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Lusha to Claude?
Connect Lusha in Elaichi, then paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. Lusha connects with an API key, so the sign-in step is pasting the key from your Lusha account settings into Elaichi. There is no OAuth application to register and no client ID or secret to generate. Once added, Claude signs you in through Elaichi and Lusha is ready to answer.
Does Lusha work with ChatGPT and Cursor as well as Claude?
Yes. The same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. Connect Lusha once in Elaichi and every client picks it up.
What can an AI agent actually do with my Lusha data?
An agent can search Lusha for contacts and companies by title, industry, size or location, enrich a name or domain with phone numbers, emails and firmographics, find lookalikes of your best accounts, and pull ICP fit scores, signal scores, buying groups and website visits. It can also check how many Lusha credits your account has used. Short, specific asks work better than long paragraphs.
Does connecting Lusha give the AI my whole account and all my credits?
No. Every Lusha call runs under the API key of the person who signed in to Elaichi, so the agent can only use the credits and plan features that person already has in Lusha. Elaichi can narrow that further with roles and restrictions, but it never widens it.
Can I stop an agent from spending Lusha credits or changing things?
Yes. Restrictions in Elaichi apply per action, on a role or on one person, so you can keep enrichment, which spends Lusha credits, to a few people while everyone else can still search. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Lusha connection when someone leaves?
Offboarding someone in Elaichi ends their Lusha access at once, across Claude, ChatGPT, Cursor and every other client. A shared Lusha connection keeps working for everyone else on the team. If you disconnect Lusha once in Elaichi, it disappears from every client at the same time.
Does the Lusha MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lusha is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Lusha?
Yes. Both let Claude, ChatGPT or Cursor use Lusha. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Lusha call.
How is Elaichi different from Composio for Lusha?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Lusha: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Lusha in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot