Skip to main content

Lusha Model Context Protocol (MCP) Server

Written by Einat Bechor
Updated this week

The Lusha MCP Server brings enterprise-grade B2B contact and company data directly to your AI conversations. Built on Lusha's database of 100+ million business contacts and 60+ million companies, it enables AI assistants to find, verify, enrich, and prospect contacts and companies through natural language - without writing API calls or managing technical integrations.

MCP (Model Context Protocol) is an open standard that allows AI assistants to securely connect to external data sources and tools. Lusha's MCP Server is compatible with Claude, ChatGPT, Cursor, VS Code, and any other MCP-supported AI client.

Features

  • Contact Data Enrichment - access verified email addresses, phone numbers, and professional profiles using email, LinkedIn URL, or name + company.

  • Company Data Enrichment - retrieve firmographics, employee counts, industry data, funding information, and business insights.

  • Bulk Processing - enrich up to 100 contacts or companies in a single request for high-volume workflows.

  • Prospecting - search Lusha's full database using structured filters (job title, seniority, location, company size, industry, and more) to build targeted prospect lists.

Requirements

  • A valid Lusha API key - Admin or Manager role required to generate one

  • A Lusha plan with sufficient credits

  • An MCP-compatible AI client (Claude, ChatGPT, Cursor, VS Code, and others)

To generate your API key, sign in to your Lusha account and visit the API section in your admin panel (dashboard.lusha.com/enrich/api).

Setup

Option 1 -Claude Remote MCP (recommended)

This is the easiest setup route. It works in Claude Web and Claude Desktop with no configuration files required. Best for non-technical users, quick pilots, and shared team setups.

  1. Open Claude and go to Settings > Connectors.

  2. Click Add custom connector.

  3. Paste the Lusha Remote MCP URL: https://mcp.lusha.com.

  4. Complete authentication via OAuth.

  5. In any chat, open the tools menu to confirm the Lusha MCP tools are available.

Option 2 - Claude Desktop (config file)

For users who prefer manual configuration or need a local setup.

Step 1 - Locate your configuration file. The claude_desktop_config.json file is in a different location depending on your OS:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

  • Linux: ~/.config/Claude/claude_desktop_config.json

If the file does not exist, create it in the appropriate directory.

Step 2 - add the following configuration:

{

"mcpServers": {

"lusha": {

"command": "npx",

"args": ["@lusha/mcp"],

"env": {

"LUSHA_API_KEY": "your_lusha_api_key_here"

}

}

}

}

Step 3 - replace your_lusha_api_key_here with your actual API key, then close and reopen Claude Desktop to load the new configuration.

Option 3 - ChatGPT

The Lusha MCP Server supports ChatGPT. An Admin must configure the connector first; individual users can then enable it.

Admin setup:

  1. In ChatGPT, go to Settings > Manage Workspace.

  2. Click Apps & Connectors > Create.

  3. Toggle on Dev Mode.

  4. Enter the following: Name: Lusha MCP / URL: https://mcp.lusha.com / add your API authentication details.

  5. Click Create, then toggle the connector ON.

User setup (after Admin has enabled the connector):

  1. In ChatGPT, go to Settings > Apps & Connectors.

  2. Find Lusha Connector and toggle Enable.

Once enabled, use natural language to access Lusha data directly in your ChatGPT conversations.

Option 4 - Cursor

  1. Go to Cursor > Settings > Cursor Settings > MCP.

  2. Add a Lusha entry with the command: npx @lusha/mcp.

  3. Set your Lusha API key in the environment variables section.

  4. Optional: enable Yolo mode (Cursor > Settings > Cursor Settings > Features > Chat > Enable Yolo mode) to approve tool calls automatically.

Available tools

The Lusha MCP Server provides the following tools. For prospecting, always start with the prospecting_search_guide tool before using filters or search — it provides step-by-step workflow guidance and helps avoid unnecessary credit usage.

Category

Tool

Description

Contact Data

contacts_search

Enrich contact information using email, LinkedIn URL, or name + company. Up to 100 contacts per request.

Company Data

companies_search

Get comprehensive company data using domain or company name. Up to 100 companies per request.

Prospecting - Guide

prospecting_search_guide

Start here. Step-by-step guidance for optimal prospecting workflows. Call this first before any prospecting tool.

Prospecting -Companies

prospecting_company_filters

Get available filter options for company prospecting. No credits charged.

prospecting_company_search

Search companies by firmographic and technographic filters (domains, technologies, intent topics, sizes, revenues, SIC/NAICS codes).

prospecting_company_enrich

Enrich companies by ID for detailed firmographic and technographic data. May consume credits.

Prospecting -Contacts

prospecting_contact_filters

Get available filter values for contact search. No credits charged.

prospecting_contact_search

Search for contacts using structured filters (company, location, department, seniority, and more).

prospecting_contact_enrich

Enrich contacts by ID to reveal emails and phone numbers. Consumes credits.

Tip: Recommended prospecting workflow: prospecting_search_guide first → use filter tools to preview valid values (no credits) → search → enrich only the results you want.

Example prompts

Getting started with prospecting

  • "How should I use Lusha for prospecting?" - starts the guide tool for optimal workflow guidance.

Enrichment

  • "Can you get Yoni Tserruya's email from Lusha?"

  • "Enrich this list of email addresses with full contact details: [email1], [email2], [email3]"

  • "Get company information for Lusha, including employee count, industry, and location."

  • "Get company details for these domains: microsoft.com, salesforce.com, hubspot.com"

  • "Find contact details for this LinkedIn profile: linkedin.com/in/johnsmith"

Prospecting

  • "Find 15 senior directors of IT at 200-1,000 employee SaaS companies in the UK. Enrich the top 5 with work email and mobile."

  • "Find 10 contacts in Boston working at technology companies."

  • "Search for marketing managers at SaaS companies in New York."

  • "Find tech companies in California with 50-200 employees."

  • "Search for companies using React with revenue over $10M."

  • "What departments and seniority levels can I filter by in Lusha?"

Credits and billing

  • Filter tools (prospecting_company_filters, prospecting_contact_filters) - no credits charged.

  • Enrichment tools (contacts_search, companies_search, prospecting_contact_enrich, prospecting_company_enrich) - credits charged per successful data match. No credits charged for failed lookups.

  • Rate limits - same as the Lusha Public API (25 requests per second). Use bulk operations when processing large volumes to reduce the number of API calls.

Monitor your credit usage in the Lusha Analytics or via the Credit Usage API.

Security

  • Store your API key in secure credentials - use your AI client's built-in credentials manager or OS keychain. Never paste it in plain text in a chat.

  • Limit tool permissions in Claude Connectors to the minimum needed for your workflow.

  • Rotate your API key periodically and remove unused connectors from your AI clients.


Troubleshooting

Tools not appearing in Claude

Confirm the connector has been added and that you have permission to use tools in Claude settings. Restart the app and try again.

"API Key Not Found" error

  • Verify your API key is correctly set in the configuration file or environment variables.

  • Confirm API access is enabled on your Lusha plan (Admin or Manager role required).

  • Check that the key has not been regenerated since you set it up.

"No Results Found"

  • Try a different identifier - email, LinkedIn URL, or full name + company.

  • Verify the contact or company exists in Lusha's database.

  • Check for typos in the provided information.

Partial or no results returned

Credits follow standard API rules - no charge on failed lookups. If your account has geographic restrictions, some fields may return as null for compliance reasons.

Did this answer your question?