Lusha MCP Server

The Lusha MCP Server is the official Model Context Protocol integration for Lusha, giving AI agents direct access to Lusha's B2B database of business contacts and companies. It exposes contact enrichment, company enrichment, and a multi-step prospecting workflow (filter, search, enrich) so an agent can build targeted prospect lists and pull verified emails, direct dials, and firmographics inside a chat session.

Lusha offers two deployment paths. The recommended option is the hosted remote server at https://mcp.lusha.com, which is supported by Claude (Web and Desktop via the connector directory), ChatGPT, VS Code/GitHub Copilot, Cursor, and n8n. Authentication uses a Bearer token containing your Lusha API key. A self-hostable open-source version is also published as the npm package @lusha-org/mcp from the lusha-oss/lusha-public-api-mcp repository for local stdio-based use.

Bulk endpoints accept up to 100 records per request, which makes Lusha well suited to list-building and CRM enrichment workflows. Standard Lusha credit rules apply: failed lookups are not charged, and account-level geographic and compliance restrictions are enforced at the API level.

Tools

Prerequisites

• A Lusha account with API access (find your key under Admin Panel, API section).
• An MCP-compatible client (Claude, ChatGPT, Cursor, VS Code, n8n).

Option 1: Hosted remote server (recommended)

The hosted endpoint is https://mcp.lusha.com. Authenticate with a Bearer token.

Claude (Web and Desktop)

Visit claude.ai/directory/connectors/lusha and complete the connector flow.

Cursor

Edit ~/.cursor/mcp.json (macOS/Linux) or %APPDATA%\Cursor\mcp.json (Windows):

{
  "mcpServers": {
    "lusha": {
      "url": "https://mcp.lusha.com",
      "headers": {
        "Authorization": "Bearer YOUR_LUSHA_API_KEY"
      }
    }
  }
}

VS Code (GitHub Copilot)

Add to settings.json:

{
  "mcp": {
    "servers": {
      "lusha": {
        "type": "http",
        "url": "https://mcp.lusha.com",
        "headers": {
          "Authorization": "Bearer YOUR_LUSHA_API_KEY"
        }
      }
    }
  }
}

n8n

Use the MCP Client Tool node (n8n 1.88.0+). SSE endpoint: https://mcp.lusha.com/sse. Add header Authorization: Bearer YOUR_LUSHA_API_KEY.

Option 2: Self-hosted (stdio via npm)

Install the open-source package and configure your client to launch it locally:

{
  "mcpServers": {
    "lusha": {
      "command": "npx",
      "args": ["@lusha-org/mcp@latest"],
      "env": {
        "LUSHA_API_KEY": "your_lusha_api_key_here"
      }
    }
  }
}

Supported environment variables: LUSHA_API_KEY (required), LOG_LEVEL, LUSHA_TIMEOUT, DISABLE_SSL (dev only). The self-hosted version exposes personBulkLookup and companyBulkLookup.

• Enrich a list of LinkedIn URLs or work emails with verified phone numbers and direct dials for an SDR outbound sequence.
• Build a target account list by filtering on industry, headcount, and geography, then auto-enrich the matching companies with firmographics.
• Find decision-makers at a set of named accounts by filtering on job title and seniority, then pull contact info in one step.
• Append missing email, phone, and title data to CRM records during a nightly sync or ad hoc cleanup.
• Validate that a prospect's email and role are still accurate before a sales rep reaches out.

• "Find the VPs of Engineering at companies in the 200 to 1000 employee range in Germany and return their work emails."
• "Enrich these 50 LinkedIn URLs with verified phone numbers and current job titles."
• "Look up Acme Corp by domain acme.com and tell me their industry, employee count, and HQ location."
• "Search Lusha for CFOs at US SaaS companies with more than 50M in revenue, then enrich the top 25."
• "I have a CSV of names and company domains. Get me verified emails for everyone on the list."

• Official, vendor-maintained server with a hosted HTTP endpoint and an open-source npm package option.
• Broad coverage: contact and company enrichment plus a full prospecting workflow (filters, search, enrich).
• Bulk endpoints support up to 100 records per call, suitable for list-building and CRM sync.
• Compatible with all major MCP clients including Claude, ChatGPT, Cursor, VS Code, and n8n.

• Requires a paid Lusha plan with API access; credits are consumed on successful lookups.
• Data quality and coverage vary by region and seniority, and account-level geographic restrictions apply.
• The self-hosted npm package exposes fewer tools (bulk lookup only) than the hosted remote server.

• Apollo.io MCP server for combined prospecting and outreach data.
• Clearbit / HubSpot Breeze enrichment for company firmographics enrichment inside HubSpot.
• ZoomInfo as a larger-database B2B contact data alternative (no first-party MCP at time of writing).