The Lusha MCP Server brings enterprise-grade B2B contact and company data directly to your AI conversations. Built on Lusha's comprehensive database of 100+ million business contacts and 60+ million companies, this MCP server enables AI assistants to find, verify, and enrich prospect information through natural language.
| Feature | Description |
|---|---|
| Contact Data Enrichment | Access verified emails, phone numbers, and professional profiles for business contacts |
| Company Data Enrichment | Retrieve detailed firmographics, employee counts, and industry data |
| Bulk Processing | Enrich up to 100 contacts or companies in a single request |
| Prospecting | Query Lusha's database by job title, seniority, location, and more |
- A Lusha plan with sufficient credits
- A valid Lusha API key
Get your API key: Sign in to your Lusha account and navigate to the API section in your admin panel.
The easiest, UI-first route. Works in Claude Web and Claude Desktop.
- Go to claude.ai/directory/connectors/lusha
- Click Add to Claude
- Complete authentication (OAuth)
- In any chat, open the tools menu to see the Lusha MCP tools
Try it: "Find 10 marketing managers at SaaS companies in New York and enrich the top 5."
Best for: Non-technical users, quick pilots, shared team setups.
Access must be configured by account admins through Workspace Management.
- Click Settings in your ChatGPT workspace
- Click Manage Workspace > Apps & Connectors
- Click Create
- Toggle on Dev Mode
- Enter the following:
- Name: Lusha MCP
- URL:
https://mcp.lusha.com - Add your API authentication details
- Click Create, then toggle the connector ON
- Click Settings > Apps & Connectors
- Find Lusha Connector and click Enable
Once enabled, use natural language to access Lusha's data in your ChatGPT conversations.
Use the Lusha MCP Server directly in VS Code via GitHub Copilot's MCP support (available in VS Code 1.99+).
- Open the Command Palette (
Cmd+Shift+P/Ctrl+Shift+P) - Run MCP: Add Server
- Select HTTP as the server type
- Enter the URL:
https://mcp.lusha.com - Name the server
lusha - When prompted, add your Lusha API key as an authentication header
Open your VS Code settings.json and add the following under mcp.servers:
{
"mcp": {
"servers": {
"lusha": {
"type": "http",
"url": "https://mcp.lusha.com",
"headers": {
"Authorization": "Bearer YOUR_LUSHA_API_KEY"
}
}
}
}
}Replace YOUR_LUSHA_API_KEY with your actual API key.
- Open GitHub Copilot Chat (
Ctrl+Alt+I/Cmd+Alt+I) - Switch to Agent mode using the mode selector
- Click the Tools icon and enable the Lusha tools
- Ask naturally: "Find senior engineers at fintech companies in London"
Best for: Developers who want Lusha data without leaving their editor.
Cursor supports MCP servers natively through its configuration file.
Open (or create) your Cursor MCP config file:
- macOS/Linux:
~/.cursor/mcp.json - Windows:
%APPDATA%\Cursor\mcp.json
- macOS/Linux:
Add the Lusha server configuration:
{
"mcpServers": {
"lusha": {
"url": "https://mcp.lusha.com",
"headers": {
"Authorization": "Bearer YOUR_LUSHA_API_KEY"
}
}
}
}- Restart Cursor
- In Cursor Chat or Composer, the Lusha tools will be available automatically
Open Cursor Chat and ask: "What Lusha tools are available?" - Cursor will list the active MCP tools.
Best for: Developers using Cursor as their primary AI-assisted editor.
Connect the Lusha MCP Server to your n8n workflows using the built-in MCP Client Tool node. This lets your AI agent workflows call Lusha tools - prospecting, enrichment, and more - as part of any automated sequence.
Requires: n8n version 1.88.0 or higher. The MCP Client Tool node is included by default in n8n Cloud and recent self-hosted installations.
- Open your n8n instance and create a new workflow (or open an existing AI agent workflow)
- Click Add node and search for MCP Client Tool
- Add the node to your canvas and open its settings
- In the SSE Endpoint field, enter:
https://mcp.lusha.com/sse - Under Authentication, select Header Auth
- Set the header name to
Authorizationand the value to:ReplaceBearer YOUR_LUSHA_API_KEYYOUR_LUSHA_API_KEYwith your actual key from the Lusha admin panel - Under Tools to Use, select All Tools to expose the full Lusha toolset, or pick specific tools as needed
- Connect the MCP Client Tool node to your AI Agent node
- Activate the workflow
Once connected, your AI Agent node can call any Lusha tool as part of its reasoning. For example, you can prompt the agent:
- "Find 5 VP-level contacts at fintech companies in the US and enrich their emails"
- "Enrich this list of company domains with headcount and industry data"
- "Search for marketing directors at SaaS companies with 100-500 employees"
The agent will automatically discover and invoke the appropriate Lusha tools during execution.
After activating the workflow, run a test execution. Open the MCP Client Tool node output to confirm it lists the available Lusha tools. If tools are not appearing, double-check the SSE endpoint URL and that your API key is valid.
Best for: Teams building automated prospecting or enrichment pipelines, CRM sync workflows, or any multi-step AI agent sequence that needs live B2B data.
Recommended workflow:
prospecting_search_guide→ Filters (no credits) → Search → Enrich
| Category | Tool | Description |
|---|---|---|
| Contact Data | contacts_search | Enrich contact info using email, LinkedIn URL, or name + company. Up to 100 contacts per request. |
| Company Data | companies_search | Get company data using domain or company name. Up to 100 companies per request. |
| Prospecting - Guide | prospecting_search_guide | Start here. Returns step-by-step workflow guidance before using any other prospecting tools. |
| Prospecting - Companies | prospecting_company_filters | Get available filter options for company prospecting (no credits charged) |
prospecting_company_search | Search companies by firmographic/technographic filters | |
prospecting_company_enrich | Enrich companies by ID for detailed data (may consume credits) | |
| Prospecting - Contacts | prospecting_contact_filters | Get available filter values for contact search (no credits charged) |
prospecting_contact_search | Search contacts using structured filters (company, location, department, seniority, etc.) | |
prospecting_contact_enrich | Enrich contacts by ID to reveal emails and phones (consumes credits) |
- Credits: Same as the Public API. Search is low-cost discovery; enrichment is charged per data point revealed (email, phone, etc.)
- Rate limits: Same as the Public API
- State-based restrictions: If your account has geographic restrictions, MCP returns compliant results - some fields may be null
Always start with the guide for prospecting workflows:
"How should I use Lusha for prospecting?" (This triggers prospecting_search_guide first)
Enrich a contact: "Can you get Yoni Tserruya's email from Lusha?"
Bulk enrich contacts: "Enrich this list of email addresses with full contact details."
Enrich a company: "Get company information for Lusha."
Bulk enrich companies: "Get company details for these domains: microsoft.com, salesforce.com, hubspot.com."
Search for contacts:
- "Find 10 contacts in Boston working in technology companies"
- "Search for senior directors in IT at companies with 500+ employees"
- "Get marketing managers at SaaS companies in New York"
Search for companies:
- "Find tech companies in California with 50-200 employees"
- "Search for companies using React with revenue over $10M"
- "Get fintech companies that received funding in the last year"
Filter discovery:
- "What departments can I filter by in Lusha?"
- "Show me available seniority levels for contact search"
- "What industry categories are available for company search?"
Enrichment after search:
- "Get the email and phone for the first 5 contacts from that search"
- "Enrich those companies with full details including funding and revenue"
- "Get mobile numbers for contacts who have them available"
| Issue | Resolution |
|---|---|
| Tools not showing in Claude | Confirm the connector is added and you have permission to use tools. Restart the app. |
| Tools not showing in VS Code | Make sure you're in Agent mode in Copilot Chat. Check that mcp.servers is correctly formatted in settings.json. |
| Tools not showing in Cursor | Verify mcp.json is in the correct path and properly formatted JSON. Restart Cursor fully. |
| Tools not showing in n8n | Confirm the MCP Client Tool node is connected to your AI Agent node and the workflow is activated. Check that the SSE endpoint URL ends in /sse and the API key header is correctly formatted. |
| Partial or no results returned | Credits follow API rules - no charge on failed lookups. Check your remaining credits in the Lusha admin panel. |
| Auth errors | Confirm your API key is valid and correctly formatted in your config (no extra spaces or line breaks). |
- Store API keys in secure credentials (OS keychain, password manager, or your editor's secrets manager) - avoid hardcoding them in shared config files
- In n8n, use the built-in Credentials system to store your API key rather than pasting it directly into node fields
- Limit tool permissions to the minimum needed for your use case
- Rotate API keys periodically and remove unused connectors
- For team setups, use environment variables rather than committing keys to version control
- Lusha API Documentation - Complete API reference
- MCP Protocol Specification - Learn about Model Context Protocol
- n8n MCP Client Tool Docs - n8n official MCP node reference
- Data Compliance Guide - Privacy and security information