> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lusha.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP tools reference

> Every tool the Lusha MCP server exposes, grouped by category.

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](https://docs.lusha.com/faq/api.md) and [credits FAQ](https://docs.lusha.com/faq/billing.md).

> [!NOTE]
>
> 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.

> [accordion] Known contacts and companies (2)
>
> | Tool | What it does |
> | - | - |
> | `contacts_search` | Enrich contact data using email, LinkedIn URL, or name + company. |
> | `companies_search` | Retrieve company data using domain or company name. |

> [accordion] Prospecting (6)
>
> | Tool | What it does |
> | - | - |
> | `prospecting_contact_filters` | Get available filter values for contact prospecting (no credits charged). |
> | `prospecting_contact_search` | Search contacts by job title, seniority, location, department, and more. |
> | `prospecting_contact_enrich` | Enrich contacts by ID to reveal emails and phones (credits consumed). |
> | `prospecting_company_filters` | Get available filter values for company prospecting (no credits charged). |
> | `prospecting_company_search` | Search companies by firmographic and technographic filters. |
> | `prospecting_company_enrich` | Enrich companies by ID for detailed firmographic data. |

> [accordion] Buying group (2)
>
> | Tool | What it does |
> | - | - |
> | `buying_group_search` | Find the buying committee at a target account. |
> | `decision_makers_buying_group_search` | Identify the decision makers within that committee. |

> [accordion] Bulk enrichment jobs (3)
>
> | Tool | What it does |
> | - | - |
> | `contacts_enrich_job_list` | List background bulk contact enrichment jobs. |
> | `contacts_enrich_job_status` | Check the status of a bulk enrichment job. |
> | `contacts_enrich_job_results` | Retrieve the results of a completed bulk enrichment job. |

> [accordion] Lookalikes (2)
>
> | Tool | What it does |
> | - | - |
> | `lookalike_contacts` | Find contacts similar to a seed contact. |
> | `lookalike_companies` | Find companies similar to a seed company. |

> [accordion] Signals and intent (9)
>
> | Tool | What it does |
> | - | - |
> | `signals_contact_filters` | Get available filter values for contact signals (no credits charged). |
> | `signals_contacts_search` | Find people by trigger events such as promotions and job changes. |
> | `signals_contacts_get` | Get signals for known contacts by ID. |
> | `signals_company_filters` | Get available filter values for company signals (no credits charged). |
> | `signals_companies_search` | Find accounts by trigger events such as funding, hiring surges, and headcount growth. |
> | `signals_companies_get` | Get signals for known companies by ID. |
> | `signal_score_contacts` | Score contacts by signal strength. |
> | `signal_score_companies` | Score companies by signal strength. |
> | `website_visits_search` | See which companies are visiting your website. |

> [accordion] Recommendations and scoring (5)
>
> | Tool | What it does |
> | - | - |
> | `recommendations_contacts` | Get paginated, scored contact recommendations with signals and Target Profile attribution. |
> | `recommendations_companies` | Get paginated, scored company recommendations with signals and Target Profile attribution. |
> | `recommendations_contacts_filters` | Get valid signal types and Target Profiles for filtering contact recommendations. |
> | `recommendations_companies_filters` | Get valid signal types and Target Profiles for filtering company recommendations. |
> | `predictive_score_companies` | Score companies by how well they fit your Target Profile. |
>
> > [!NOTE]
> >
> > 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.

> [accordion] Tables (13)
>
> | Tool | What it does |
> | - | - |
> | `table_create` | Create a workspace table. |
> | `table_list` | List the tables in your workspace. |
> | `table_update` | Rename a table or change its settings. |
> | `table_delete` | Delete a table. |
> | `table_status` | Check whether a table's columns have finished running. |
> | `table_add_entities` | Add contacts or companies as rows. |
> | `table_get_entities` | Read the rows in a table. |
> | `table_remove_entities` | Remove rows from a table. |
> | `table_columns_catalog` | List the columns available to add (no credits charged). |
> | `table_add_columns` | Add enrichment or AI columns to a table. |
> | `table_list_columns` | List the columns currently on a table. |
> | `table_remove_column` | Remove a column from a table. |
> | `table_run_column` | Run a column across every row in the table. |
>
> > [!NOTE]
> >
> > These mirror the Tables REST endpoints. See the [Contact Tables](https://docs.lusha.com/api-reference/contacts-tables/create-contacts-table.md) and [Company Tables](https://docs.lusha.com/api-reference/companies-tables/create-companies-table.md) reference for full schemas.

> [accordion] CRM (4)
>
> | Tool | What it does |
> | - | - |
> | `get_supported_integrations` | List the CRMs Lusha can connect to, your connection state, and per-platform export limits. |
> | `connect_crm` | Generates a secure OAuth link to connect (or reconnect) a CRM. Admin-only - if a non-admin asks, the agent points them to their account admin instead of generating a link. |
> | `export_contacts_to_crm` | Push selected or enriched contacts into the connected CRM. |
> | `export_companies_to_crm` | Push selected or enriched companies into the connected CRM, where the CRM supports it. |
>
> 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.
>
> > [!NOTE]
> >
> > 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.

> [accordion] Conversations (2)
>
> | Tool | What it does |
> | - | - |
> | `conversations_search` | Search call recordings. |
> | `conversations_transcript_get` | Pull the transcript for a specific call. |

> [accordion] Account (2)
>
> | Tool | What it does |
> | - | - |
> | `account_usage` | Check credit balance, rate-limit status, and plan info. |
> | `purchase_options` | See available plans and credit packs. |

## 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.


## Related topics

- [Lusha Model Context Protocol (MCP) Server](https://docs.lusha.com/user-guide/mcp/lusha-model-context-protocol-mcp-server.md)
- [MCP prompt examples](https://docs.lusha.com/mcp/examples.md)
- [MCP FAQ](https://docs.lusha.com/faq/mcp.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.