Lusha

Name: Lusha MCP Server
Availability: InStock
Author: Lusha

Productivity24 tools

Search B2B contacts and companies, reveal verified emails and phone numbers, and pull buying signals from your AI assistant. 24 tools, OAuth sign-in, reveals consume Lusha credits.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Lusha via MCP

https://mcp.lusha.com/mcp/claude

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Lusha Tools & Capabilities (24)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The output is other people's personal data, and your obligations start when it arrives. Lusha states it relies on legitimate interest and does not collect opt-in consent from individuals for third-party outreach, and places responsibility for a valid legal basis and for honouring opt-outs on the customer. Its API terms require you to delete personal information if the individual asks.
Opt-out suppression does not reach a transcript. Lusha suppresses opted-out contacts from future output, but details already pulled into a conversation, a document or a CRM are yours to remove. Opt-out reports go to an account Admin monthly, or to a webhook — not to the agent.
An agent enriching in a loop can spend an allowance fast. At 5 credits per phone number, a hundred-contact list revealed with phones is 500 credits before emails. Requests returning no results still cost the 1-credit minimum. Per-user credit caps exist only on Premium and Scale plans, and legacy Premium plans are excluded from that feature.
There is no read-only grant. The server advertises a single mcp scope, and the authorization server's extra api_access scope is a platform scope rather than a narrower alternative. Per-call approval in your client is the granular control.
A paid plan and an elevated role are both required. Lusha lists a paid plan with API credits plus an Admin or Manager role, so there is no reduced-privilege way to connect.
Coverage is uneven and Lusha says so. Lusha states no B2B data provider has 100% coverage or accuracy, that quality varies by region, industry and seniority, that its coverage is stronger for English-speaking markets and technology industries, and that phone coverage varies significantly by country. Emails carry a high/medium/low confidence score.
You cannot correct a record through the connector. Lusha does not support manual updates to contact information; corrections run through automated algorithms, a thumbs-down in the platform, or a CSV submission.
Do Not Call filtering is Scale-only and covers two countries. UK (TPS and CTPS) and USA, with an Admin enabling it. Lusha warns that calling a registered number may result in significant fines.
The published tool lists disagree with each other. The directory names 24 and Lusha's MCP table lists 22, with renames in one direction and three directory-only tools in the other. Two further names appear only in Lusha's narrative docs. Lusha's own note says available tools may vary by client.
Tool parameters and safety annotations were not readable. All three live endpoints returned HTTP 401 to an anonymous initialize on 2026-08-18, so names came from the directory snapshot and meanings from Lusha's documentation. No tool was called and no person was looked up.

Frequently asked questions

Does the Lusha MCP server cost credits to use?

Yes, but only when you reveal contact data. Lusha charges 1 credit per email revealed and 5 credits per phone number, with search, filtering and company browsing at 0 credits. Its documentation states MCP calls consume API credits, and that API requests carry a 1-credit minimum even when no results come back.

What plan do you need for the Lusha MCP server?

A paid Lusha plan with available API credits. Lusha's setup article lists a paid plan and an Admin or Manager role as requirements, because generating an API key needs that role. Lusha sells Free, Starter, Pro, Premium and Scale tiers, and its Do Not Call filtering feature is restricted to Scale plans only.

How do you connect Lusha to a client other than Claude?

Use the bare host with an API key header. Lusha's documentation gives OAuth for Claude, ChatGPT and Codex only, and tells every other client — Cursor, VS Code, n8n, Gemini CLI — to point at https://mcp.lusha.com and pass an x-api-key header. Lusha notes the header name must be lowercase or authentication fails.

Whose personal data does the Lusha connector return?

Third parties who never gave Lusha their data directly. Lusha aggregates business contact details from public professional profiles, company websites, business directories and contributed sources. It states it relies on legitimate interest as its legal basis and does not collect opt-in consent from individuals for third-party outreach.

How can someone remove their details from Lusha?

Through Lusha's removal form or its privacy team. Lusha documents an automated removal form and a privacy address, and states submitted details are permanently deleted. Opted-out contacts are suppressed from search, enrichment and any Lusha output. Bulk removal through the form is not available, so multiple records need the privacy team directly.

Will an agent tell you when a contact has opted out?

No — opt-out reporting runs outside the connector. Lusha sends CSV opt-out reports to a designated account Admin, typically monthly, covering only contacts who opted out since the previous report. Lusha also offers an opt-out webhook for real-time notification. Building a full suppression list means aggregating every report you have received.

Can the Lusha MCP server spend money without you noticing?

It can spend credits, and Anthropic's snapshot names a purchase_options tool. Reveals deduct credits automatically, and Lusha documents an in-conversation top-up flow on its Claude cards. Lusha lets Admins cap credits per user or group on Premium and Scale plans, which is the control that limits an agent's spend.

What are the Lusha API rate limits?

Twenty-five requests per second on general endpoints. Lusha's API documentation adds 5 requests per minute for the Account Usage API and 100 per minute for the Webhooks API, and returns remaining quota in response headers such as x-rate-limit-minute. Exceeding a limit or a daily quota returns HTTP 429.