# 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.

Source: https://elaichi.ai/connectors/lusha/

## Facts

| | |
| --- | --- |
| Application | Lusha |
| Category | Sales Intelligence |
| AI tools | 68 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Lusha is connected

- 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?

## Connect Lusha in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Lusha.
2. Optionally set Share with, then press Connect.
3. Paste a Lusha API key. One person generates a token in Lusha and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Lusha tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Lusha MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Lusha MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Lusha tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Lusha through Elaichi

### Fill in a contact before the first call

Sales. Ask for the direct dial, email and current title of a prospect, enriched from Lusha, before you pick up the phone.

### Build a prospect list from one description

Sales development. Describe the title, industry, company size and location you want and get a list of matching Lusha contacts, already enriched.

### Find lookalikes of your best customers

Marketing. Hand over a few accounts that closed and get Lusha companies that look like them, ready to drop into a campaign.

### Score an inbound list against your ICP

Revenue operations. Paste in a batch of companies and get each one's ICP fit score and signal score so reps work the right ones first.

### Map the buying group at a target account

Sales. Ask who else at a company is involved in the decision and get the Lusha buying group with their roles and contact details.

### Spot accounts showing intent this week

Customer success. Check which target companies have visited your website or set off a signal in Lusha, and plan outreach around it.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Lusha connection?

Yes. One person connects Lusha in Elaichi with their API key and shares the connection with a team, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every Lusha search and enrichment.

### 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.

## All 68 Lusha tools

Every tool below is callable through https://api.elaichi.ai/mcp once Lusha is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Lusha person** (List). Look up and enrich one person with Lusha's legacy V2 API by name plus company, email, LinkedIn URL, or personId. Returns contact.data (names, emails, phones, location, jobTitle, socialLinks, company); empty when not found. revealEmails/revealPhones need the Unified Credits plan. V2 ends November 30, 2026.
- **Get single Lusha contact enrich job by ID** (Get). Poll a Lusha contacts enrichment job started via Enrich Contacts. Returns: jobId, status, requestId, expiresAt, retryAfter, covers, contacts, creditsCharged, reason. While status is processing, wait retryAfter seconds and poll again. Required: id.
- **Get single Lusha contact prospecting filter by ID** (Get). Get the valid values for a Lusha contact prospecting filter type. Returns: values. id is the filter type: one of departments, seniority, existingDataPoints, countries, locations. locations also requires a query of 2-256 characters. Required: id.
- **List all Lusha contact prospecting filters** (List). List the filter types available for Lusha contact prospecting. Returns each filter with its filterType (such as departments, seniority, existingDataPoints, countries, locations) and a requiresQuery flag showing which filter types need a search query. Use a filter type with the filter values endpoint before building a prospecting request.
- **Lusha contacts enrich** (Action). Reveal full contact data for up to 100 Lusha contacts you already found via search, by passing their ids. Returns: requestId, results, tableWrite, billing, status, statusDescription, statusReason, job. Required: ids. Credits charged per revealed email or phone; polling the job is free.
- **List all Lusha contacts** (List). Prospect Lusha contacts by contact and company filters (title, seniority, department, location, data points). Returns non-PII previews: id, firstName, lastName, jobTitle, company, location, socialLinks, has. Required: filters. limit: integer 10-100, default 100; same value with next_cursor. Max 50,000 results. Credits per result and matched signal.
- **Lusha contacts search** (Search). Look up up to 100 Lusha contacts by id, linkedinUrl, email, or firstName + lastName + companyName/companyDomain, one identifier per contact. Returns a non-PII preview (no emails or phones): id, firstName, lastName, jobTitle, company, location, socialLinks, has, canReveal. Required: contacts. Credits charged per successful result.
- **Lusha contacts search and enrich** (Search). Find up to 100 Lusha contacts by identifier and reveal their full data in one call (Search plus Enrich). Returns enriched records: id, firstName, lastName, fullName, emails, phones, tags, previousEmployment, updateDate; never a job to poll. Required: contacts. Credits charged for the search and per revealed field.
- **Lusha contacts lookalikes** (Action). Find contacts similar to 5-100 seed contacts (LinkedIn URLs, emails, Lusha ids, or name + company). Returns dedupeSessionId, results (contact previews), meta, tableWrite and billing; pass dedupeSessionId back to get more results without repeats. Credits: charged per result (lookalikeContact).
- **Lusha contacts signals** (Action). Get signal events (promotion, companyChange, or allSignals) for up to 100 contact ids, optionally since startDate. Returns results, startDate, endDate, tableWrite and billing. Pass tableId to also write the contacts into a table. Credits: charged per matched signal per result (showSignalsContact).
- **Lusha contacts signal score** (Action). Score up to 100 contacts by their active buying signals (0 to 1). Each contact is identified by id, linkedinUrl, email, or firstName + lastName + companyName/companyDomain. Returns requestId, results (score, NOT_FOUND or NO_SCORE entries) and billing. Credits: 1 per scored row (signal_score_contact_reveal) once that action is on the account pricebook; free until then.
- **Lusha contacts icp fit score** (Action). Score how well 1-100 contacts fit 1-3 active Target Profiles (targetProfileIds from icp_profiles list), from 0 to 1. Returns requestId, results (scored, NOT_FOUND or NO_SCORE entries) and billing. Credits: 1 per scored contact, a score of 0 included; error rows are free.
- **Lusha contacts buying group** (Action). Find the buying group (decision_maker, potential_champion, end_user) inside target companies given by domain or Lusha company id. Returns requestId, results grouped by company, pagination and billing. Page with the body pagination object. Credits: charged per contact returned (buyingGroupContact).
- **List all Lusha account usage** (List). Get a snapshot of your Lusha account usage, credit balance, rate limits, plan details, and per-action credit pricing. Returns: credits, rateLimits, plan, pricing.
- **Lusha companies enrich** (Action). Enrich up to 100 Lusha companies by id to reveal firmographics, technologies, funding, social links, open jobs and ownership. Returns: requestId, results, tableWrite, billing. Required: ids. Premium fields (e.g. competitors, intent, directParent, ultimateParent) come only when named in reveal. Credits per company revealed, plus per premium field.
- **List all Lusha companies** (List). Prospect Lusha companies by filters (size, revenue, industry, technologies, locations, intent, signals). Returns previews: id, name, domain, employeeCount, industry, location, socialLinks, has, canReveal. Required: filters. limit: integer 10-100, default 100; same value with next_cursor. Max 50,000 results. Credits per result and matched signal.
- **Lusha companies search** (Search). Look up up to 100 Lusha companies by id, name, or domain and preview each profile. Returns: requestId, results, billing. Required: companies. Each result's has and canReveal fields show which data points Enrich can unlock. Credits charged per successful result.
- **Lusha companies search and enrich** (Search). Find up to 100 Lusha companies by id, name, or domain and reveal their full data in a single call. Returns: requestId, results, billing. Required: companies. Premium fields are returned only when named in reveal. Credits charged per result plus per revealed premium field.
- **Lusha companies lookalikes** (Action). Find companies similar to 5-100 seed companies (domains or LinkedIn URLs). Returns dedupeSessionId, results (company previews), meta, tableWrite and billing; pass dedupeSessionId back to get more results without repeats. Credits: charged per result (lookalikeCompany).
- **Lusha companies signals** (Action). Get signal events (hiring, headcount, web traffic, IT spend, news, intent, or allSignals) for up to 100 company ids, optionally since startDate. Returns results, startDate, endDate, tableWrite and billing. Credits: charged per matched signal per result (showSignalsCompany); no match, no charge.
- **Lusha companies signal score** (Action). Score up to 100 companies by their active buying signals (0 to 1). Each company is identified by exactly one of id, domain, name or email. Returns requestId, results (score, NOT_FOUND or NO_SCORE entries) and billing. Credits: 1 per scored row (signal_score_company_reveal) once that action is on the account pricebook; free until then.
- **Lusha companies icp fit score** (Action). Score how well 1-100 companies fit 1-3 active Target Profiles (targetProfileIds from icp_profiles list), from 0 to 1. Returns requestId, results (scored, NOT_FOUND or NO_SCORE entries) and billing. Credits: 1 per scored company, a score of 0 included; error rows are free.
- **Lusha companies website visits** (Action). Rank companies that visited your tracked domains in a date range (at most 3 months). Domains must be set up for tracking in the Lusha dashboard, or the whole request fails with 400. Returns requestId, results (company preview plus visit metrics), pagination and billing. Credit cost is not documented. Lusha marks this endpoint Beta.
- **Get single Lusha company prospecting filter by ID** (Get). Get the valid values for a single company prospecting filter type in Lusha. Returns: values. id is the filter type: one of names, sizes, revenues, locations, sics, naics, industriesLabels, intentTopics, technologies. names, technologies, and locations also require a query of 2-256 characters. Required: id.
- **List all Lusha company prospecting filters** (List). List the filter types available for company prospecting in Lusha (such as names, sizes, revenues, locations, sics, naics, industriesLabels, intentTopics, technologies) and whether each requires a search query. Returns: filterType, requiresQuery.
- **List all Lusha account usage stats** (List). Get the credit usage of your Lusha account from the version-less GET /account/usage endpoint (used, total and remaining credits per credit type). Unlike account_usage.list (GET /v3/account/usage) it does not return rate limits, plan or pricing. Limited to 5 requests per minute. Returns: usage.
- **List all Lusha contact signal types** (List). List the signal types supported for contacts. Returns each signal type name as a plain string. No credit cost is documented.
- **Create a Lusha contact table** (Create). Create an empty contacts table, optionally seeded with ids. Required: name, owner. Returns the created table. owner.email (a user on the Lusha account) is required on table calls made with an API key; GET and DELETE table calls take it as the email query parameter instead. Free. ids is rejected; add rows via entities.
- **List all Lusha contact tables** (List). List contacts tables owned by owner.email plus tables shared with the account, optionally filtered by name and status. Over the REST proxy pass owner[email], name and status as query parameters (they are copied into the request body). owner.email (a user on the Lusha account) is required on table calls made with an API key; GET and DELETE table calls take it as the email query parameter instead. Pages 0-100 only (at most 10,100 tables). Free.
- **Get single Lusha contact table by ID** (Get). Get a contacts table by id: its metadata and processing status. owner.email (a user on the Lusha account) is required on table calls made with an API key; GET and DELETE table calls take it as the email query parameter instead. Free.
- **Update a Lusha contact table by ID** (Update). Rename a contacts table, change its visibility, archive it or reassign its owner. Send only the fields that change; owner is required. Returns the updated table. Free.
- **Delete a Lusha contact table by ID** (Delete). Permanently delete a contacts table and all its data by id. Returns tableId and status. owner.email (a user on the Lusha account) is required on table calls made with an API key; GET and DELETE table calls take it as the email query parameter instead. Free.
- **List all Lusha contact table entities** (List). Read rows of a contacts table (table_id) with every column value and per-cell status. Pages 0-100 only, so at most 10,100 rows can be read. Credits: charged per row returned (export_api). email is required with an API key (else 400).
- **Create a Lusha contact table entity** (Create). Add up to 500 contacts ids to a table (table_id). Already-present ids are reported and unresolvable ids come back in invalidIds. Free.
- **Lusha contact table entities bulk delete** (Delete). Remove specific contacts ids from a table (table_id). Required body: entityIds, owner. Returns the removal result. Free.
- **List all Lusha contact table columns** (List). List the columns already on a contacts table (table_id), with type and per-cell status counts. Free. email is required with an API key (else 400).
- **Create a Lusha contact table column** (Create). Add up to 10 Lusha columns to a contacts table (table_id), as columns [{columnKey}] or one columnKey (keys from contact_column_catalog). Enrichment starts on all rows at once. Returns one entry per requested column with its own status. Free today.
- **Delete a Lusha contact table column by ID** (Delete). Remove a column (id) and all its cell data from a contacts table (table_id). Default Lusha columns cannot be removed. Returns tableId, columnId and removed. Free. email is required with an API key (else 400).
- **Lusha contact table columns run** (Run). Populate or refresh one column (column_id) of a contacts table (table_id) asynchronously; runScope is all, missing or specific (with entityIds). Poll contact_tables get for progress. Credits: charged per row processed at the column's credit tier. runScope all charges again for rows that already have data; missing is cheapest.
- **List all Lusha contact column catalog** (List). List every Lusha column that can be added to a contacts table, with category, displayName, columnKey and type. Free.
- **List all Lusha company signal types** (List). List the signal types supported for companies. Returns each signal type name as a plain string. No credit cost is documented.
- **Create a Lusha company table** (Create). Create an empty companies table, optionally seeded with ids. Required: name, owner. Returns the created table. owner.email (a user on the Lusha account) is required on table calls made with an API key; GET and DELETE table calls take it as the email query parameter instead. Free. ids is rejected; add rows via entities.
- **List all Lusha company tables** (List). List companies tables owned by owner.email plus tables shared with the account, optionally filtered by name and status. Over the REST proxy pass owner[email], name and status as query parameters (they are copied into the request body). owner.email (a user on the Lusha account) is required on table calls made with an API key; GET and DELETE table calls take it as the email query parameter instead. Pages 0-100 only (at most 10,100 tables). Free.
- **Get single Lusha company table by ID** (Get). Get a companies table by id: its metadata and processing status. owner.email (a user on the Lusha account) is required on table calls made with an API key; GET and DELETE table calls take it as the email query parameter instead. Free.
- **Update a Lusha company table by ID** (Update). Rename a companies table, change its visibility, archive it or reassign its owner. Send only the fields that change; owner is required. Returns the updated table. Free.
- **Delete a Lusha company table by ID** (Delete). Permanently delete a companies table and all its data by id. Returns tableId and status. owner.email (a user on the Lusha account) is required on table calls made with an API key; GET and DELETE table calls take it as the email query parameter instead. Free.
- **List all Lusha company table entities** (List). Read rows of a companies table (table_id) with every column value and per-cell status. Pages 0-100 only, so at most 10,100 rows can be read. Credits: charged per row returned (export_api). email is required with an API key (else 400).
- **Create a Lusha company table entity** (Create). Add up to 500 companies ids to a table (table_id). Already-present ids are reported and unresolvable ids come back in invalidIds. Credits: reveal_company per newly added company.
- **Lusha company table entities bulk delete** (Delete). Remove specific companies ids from a table (table_id). Required body: entityIds, owner. Returns the removal result. Free.
- **List all Lusha company table columns** (List). List the columns already on a companies table (table_id), with type and per-cell status counts. Free. email is required with an API key (else 400). Lusha returned 404 for this route on 2026-10-15.
- ...and 18 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
