Skip to main content
The Lusha MCP server exposes 50 tools. Most map closely to the underlying Lusha API, so the same plan, credit, and rate-limit rules that apply to the REST API apply to MCP tool calls. See the API FAQ and credits FAQ.
Available tools may vary depending on the client used to connect. Tool names and behavior can also change as Lusha ships new capabilities - ask your MCP client to list its available Lusha tools for the exact, current set.
Results are drawn from the authenticated user’s own Target Profiles (plus any shared account-level profiles) - user and account IDs are inferred from the session, never passed as inputs. If you haven’t set up a Target Profile in ICP Hub yet, you’ll be nudged to do so with each recommendations request. Recommendations refresh daily and recalculate within minutes of an ICP change.
These mirror the Tables REST endpoints. See the Contact Tables and Company Tables reference for full schemas.
Supported CRMs: Salesforce, HubSpot, Zoho, Pipedrive, and SalesLoft. Export is contacts-first - company/account export is currently limited to the CRMs that support it.Every export returns a per-row result: which records exported, which failed and why, a direct CRM link per created record, and the credits used. Connecting is free. Export charges standard per-record export credits, and only for records the CRM actually writes. Already-present, unchanged, or duplicate records cost nothing.
This is Phase 1 - synchronous export, with a per-run cap per CRM (for example, Salesforce up to 150, HubSpot up to 100 per export). For now, push larger lists across multiple runs. Async large-batch export is planned for a later phase.

Credits and rate limits

  • Lookup and search tools generally consume credits only for successful, matched results - failed lookups are not charged.
  • Filter-discovery tools (*_filters) and account_usage don’t consume credits.
  • Rate limits follow your Lusha plan, the same as the REST API. account_usage returns your current limits and remaining headroom.