# Lusha: MCP server status, API access gate and what it does > A B2B contact and company database (300M+ profiles) accessed via a browser extension, web prospecting... Official MCP, Free to start. Checked 2026-08-24. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* --- [Directory](../index.md) / [Data & Enrichment](../categories/data-enrichment.md) / Lusha # Lusha [Official MCP](../mcp/official.md) [Free to start](../gates/free.md) [Data & Enrichment](../categories/data-enrichment.md) RESEARCHED Checked 2026-08-24 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0. Vendor: [lusha.com](https://lusha.com) · entry id 01-lusha · source 01-data-enrichment.md line 84 **What it does** 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. **AI features, separated from automation with an AI label on it** Automated lead-recommendation lists and an AI email-writing assistant sit on top of the core lookup product. The core "reveal a contact" function is a straightforward database lookup, not AI - the AI features are add-ons for prioritization and copywriting. **RevOps role** Contact-level enrichment/lookup source, commonly used as one provider inside a Clay-style waterfall, or directly via the browser extension for individual/manual prospecting **MCP server** - **Status bucket**: Official MCP - **Auth**: api key (LUSHA_API_KEY) - **Parsed URLs**: 3 found in the mcp_url field The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: official mcp_url, verbatim from the file: https://github.com/lusha-oss/lusha-public-api-mcp (also https://github.com/lusha-oss/lusha-mcp-plugin; docs: https://docs.lusha.com/mcp-docs) - [https://github.com/lusha-oss/lusha-public-api-mcp](https://github.com/lusha-oss/lusha-public-api-mcp) - [https://github.com/lusha-oss/lusha-mcp-plugin](https://github.com/lusha-oss/lusha-mcp-plugin) - [https://docs.lusha.com/mcp-docs](https://docs.lusha.com/mcp-docs) **Access gate** - **Gate bucket**: Free to start - **Can a solo operator reach it**: Yes, without talking to anyone api_gate, verbatim from the file: free **API documentation** No documentation URL recorded. 263 of 293 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health: - [https://github.com/lusha-oss/lusha-mcp-plugin](https://github.com/lusha-oss/lusha-mcp-plugin) - [https://github.com/lusha-oss/lusha-public-api-mcp](https://github.com/lusha-oss/lusha-public-api-mcp) **Jobs it can do** - [Search people by criteria](../jobs/search-people-by-criteria.md) - [Enrich a person from a LinkedIn URL](../jobs/enrich-person-from-linkedin-url.md) - [Enrich a company from a domain](../jobs/enrich-company-from-domain.md) - [Find a work email address](../jobs/find-work-email.md) - [Find a phone number](../jobs/find-phone-number.md) - [Draft personalized outreach](../jobs/draft-personalized-outreach.md) - [Score and prioritize leads](../jobs/score-and-prioritize-leads.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total. **Sources** - [https://github.com/lusha-oss/lusha-public-api-mcp](https://github.com/lusha-oss/lusha-public-api-mcp) - [https://docs.lusha.com/mcp-docs](https://docs.lusha.com/mcp-docs) - [https://docs.lusha.com/user-guide/lushas-api/all-there-is-to-know-about-lushas-api](https://docs.lusha.com/user-guide/lushas-api/all-there-is-to-know-about-lushas-api) - [https://www.vendr.com/marketplace/lusha](https://www.vendr.com/marketplace/lusha) - [https://www.saleshandy.com/blog/lusha-pricing/](https://www.saleshandy.com/blog/lusha-pricing/) 5 source URLs. Raw sources field, verbatim: 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/ **Notes, verbatim from the file** 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. **Provenance** - **Entry id**: 01-lusha - **Source file**: 01-data-enrichment.md - **Source line**: 84 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).