# Lusha
ID: 01-lusha
Page: https://gtmmcps.com/tools/01-lusha
JSON: https://gtmmcps.com/data/tools/01-lusha.json
Documentation references: https://gtmmcps.com/docs/01-lusha/
Category: Data & Enrichment
MCP support: official
Testing: RESEARCHED
API access: free
Last checked: 2026-09-03
Endpoint check: repo-local; date: 2026-09-04

A B2B contact and company database (300M+ profiles) accessed via a browser extension, web prospecting platform, and bulk CSV/API enrichment for finding direct dials, emails, and company data.

## MCP links
- https://github.com/lusha-oss/lusha-public-api-mcp
- https://github.com/lusha-oss/lusha-mcp-plugin
- https://docs.lusha.com/mcp-docs

## Sources
- https://github.com/lusha-oss/lusha-public-api-mcp
- https://docs.lusha.com/mcp-docs
- https://docs.lusha.com/user-guide/lushas-api/all-there-is-to-know-about-lushas-api
- https://www.vendr.com/marketplace/lusha
- https://www.saleshandy.com/blog/lusha-pricing/
- https://docs.lusha.com/apis/openapi/person-api

## Research notes
Per Lusha's own docs, every user gets an API key by default on every plan including Free, with rate limits scaling by tier (Free/Starter: 40 req/min, 100/day; Premium: 300/min, 18,000/day). This contradicts some third-party pricing blogs claiming Free/Starter have no API access - the official docs were treated as authoritative. Self-serve seat purchasing tops out at 5 seats; beyond that, a Scale plan requires a sales quote. 2026-09-03: vendor docs state the Search Contacts endpoint (POST /v3/contacts/search) looks up contacts by "firstName + lastName + companyName or companyDomain" and returns a non-PII preview that includes linkedinUrl (https://docs.lusha.com/apis/openapi/person-api); MCP tool contacts_search is described as "Enrich contact data using email, LinkedIn URL, or name + company" (https://docs.lusha.com/mcp-docs); the docs state it is charged per successful result via the api_search action, with no unit price stated.

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: none-found

Read current vendor documentation before configuring or running commands.