lusha_add_ contacts_ table_ rowsAdd Entities to Contacts Table.
Find the right people at a target account, reveal their details only when you say so, see who changed jobs or which accounts are hiring, and save the results to a Lusha table.
PopMCPLusha
Every endpoint of Lusha's current API is here, from search, enrichment and prospecting to signals, Target Profile scores, website visitors, tables, webhooks and call transcripts. Searches come back as previews first, so you choose whose contact details to pay for.
77 tools in the full catalog: 54 read and 23 write. 35 load by default, and the rest are found with tool search.
lusha_add_ contacts_ table_ rowsAdd Entities to Contacts Table.
lusha_create_ contacts_ tableCreate Contacts Table.
lusha_list_ contacts_ tablesList Contacts Tables.
lusha_get_ company_ signalsCompany events for up to 100 Lusha company ids: headcount, hiring surges, funding and other news, website traffic, IT spend, intent.
lusha_get_ contact_ signalsJob changes and promotions for up to 100 Lusha contact ids.
lusha_list_ company_ signal_ typesGet Company Signal Types.
lusha_list_ contact_ signal_ typesGet Contact Signal Types.
lusha_score_ company_ signalsScore Companies by Signal Activity.
lusha_enrich_ prospectsFind new people by plain filters and reveal their emails and phones in one go.
lusha_find_ companiesFind new companies by plain filters: countries, size, technologies and keywords.
lusha_find_ prospectsFind new people by plain filters: job titles, seniority, departments, countries, company domains and company size.
lusha_prospect_ companiesFind new companies matching a target profile: location, size, revenue, industry, technology, intent.
lusha_prospect_ contactsFind new people matching a target profile: job title, seniority, department, location, and company size, industry, technology.
lusha_find_ companyFind one company by domain, name or Lusha id.
lusha_find_ contactFind one person by email, LinkedIn URL, Lusha id, or first and last name with a company.
lusha_list_ company_ filter_ valuesGet Company Filter Values.
lusha_list_ company_ filtersGet Company Filter Types (Discovery).
lusha_list_ contact_ filter_ valuesGet Contact Filter Values.
lusha_list_ contact_ filtersGet Contact Filter Types (Discovery).
lusha_search_ companiesLook up companies you can name, by domain, name or Lusha id, up to 100 at once.
lusha_search_ contactsLook up people you can name, by email, LinkedIn URL, or name plus company, up to 100 at once.
lusha_enrich_ companiesFull company data (industry, size, revenue, funding, technologies) for up to 100 Lusha company ids.
lusha_enrich_ contactsReveal emails and phones for up to 100 Lusha contact ids from lusha_search_contacts, lusha_prospect_contacts, lusha_find_contact_lookalikes or lusha_find_buying_group.
lusha_get_ contacts_ enrich_ jobFetch the rest of an enrichment that came back with a job.
lusha_list_ target_ profilesList your Target Profiles (ICPs), with the ids that lusha_score_contact_icp_fit and lusha_score_company_icp_fit need.
lusha_score_ company_ icp_ fitScore Companies by ICP Fit.
lusha_find_ company_ lookalikesFind companies similar to ones you already know.
lusha_find_ contact_ lookalikesFind people similar to ones you already know.
lusha_get_ conversation_ transcriptGet Conversation Transcript.
lusha_search_ and_ enrich_ companiesLook up companies you can name and get full company data in one call, up to 100 at once.
lusha_search_ and_ enrich_ contactsLook up people you can name and reveal their emails and phones in one call, up to 100 at once.
lusha_search_ conversationsSearch Conversations.
lusha_find_ buying_ groupMap who buys at up to 25 companies: decision makers, potential champions and end users.
lusha_get_ account_ usageCredits used and left, rate limits, plan and renewal dates, and what each action costs.
lusha_list_ website_ visitorsGet Website Visitors.
lusha_add_ companies_ table_ columnsAdd Columns to Companies Table.
lusha_add_ companies_ table_ rowsAdd Entities to Companies Table.
lusha_add_ contacts_ table_ columnsAdd Columns to Contacts Table.
lusha_create_ companies_ tableCreate Companies Table.
lusha_delete_ companies_ tableDelete Companies Table.
lusha_delete_ contacts_ tableDelete Contacts Table.
lusha_get_ companies_ tableGet Companies Table.
lusha_get_ contacts_ tableGet Contacts Table.
lusha_list_ companies_ column_ catalogGet Companies Column Catalog.
lusha_list_ companies_ table_ columnsList Companies Table Columns.
lusha_list_ companies_ table_ rowsRead the rows of a company table.
lusha_list_ companies_ tablesList Companies Tables.
lusha_list_ contacts_ column_ catalogGet Contacts Column Catalog.
lusha_list_ contacts_ table_ columnsList Contacts Table Columns.
lusha_list_ contacts_ table_ rowsRead the rows of a contact table.
lusha_remove_ companies_ table_ columnRemove Column from Companies Table.
lusha_remove_ companies_ table_ rowsRemove Entities from Companies Table.
lusha_remove_ contacts_ table_ columnRemove Column from Contacts Table.
lusha_remove_ contacts_ table_ rowsRemove Entities from Contacts Table.
lusha_run_ companies_ table_ columnRun Column on Companies Table.
lusha_run_ contacts_ table_ columnRun Column on Contacts Table.
lusha_update_ companies_ tableUpdate Companies Table.
lusha_update_ contacts_ tableUpdate Contacts Table.
lusha_create_ opt_ out_ subscriptionBe notified when a contact opts out of data processing, for one webhook URL.
lusha_create_ webhook_ subscriptionsCreate Subscription.
lusha_delete_ webhook_ subscriptionsDelete Subscriptions.
lusha_get_ webhook_ delivery_ statsGet Audit Log Statistics.
lusha_get_ webhook_ secretShow the account's webhook signing secret, used to check that a delivery came from Lusha.
lusha_get_ webhook_ subscriptionGet Subscription by ID.
lusha_list_ webhook_ delivery_ logsGet Audit Logs.
lusha_list_ webhook_ subscriptionsList Subscriptions.
lusha_rotate_ webhook_ secretReplace the account's webhook signing secret.
lusha_test_ webhook_ subscriptionTest Subscription.
lusha_update_ webhook_ subscriptionUpdate Subscription.
lusha_list_ company_ signal_ filter_ valuesGet Company Signal Filter Values.
lusha_list_ company_ signal_ filtersGet Company Signal Filters (Discovery).
lusha_score_ contact_ signalsScore Contacts by Signal Activity.
lusha_list_ company_ recommendation_ filtersCompany Recommendation Filters.
lusha_list_ company_ recommendationsYour ranked queue of recommended companies from your Target Profiles.
lusha_list_ contact_ recommendation_ filtersContact Recommendation Filters.
lusha_list_ contact_ recommendationsYour ranked queue of recommended people from your Target Profiles.
lusha_score_ contact_ icp_ fitScore Contacts by ICP Fit.
Credentials off one Lusha screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.
In Lusha, open API & connectors and click Copy API key. Paste it here. Every plan has a key, including Free, and there is no app to register and nothing to approve. Add the email you sign in with if you want your AI to use Lusha tables without asking for it.
••••••••••••3f7ayou@company.comSearches and reveals spend your Lusha credits the moment the AI calls them, even on a read-only connection. Changing a table, running a column across its rows and changing webhooks also take effect right away, and read-only access in PopMCP blocks those. To cap the spend, an admin or manager can set a monthly credit limit on a key they generate.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Lusha credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
How many Lusha credits do I have left, and when do they renew?
lusha_get_account_usageok
Then just ask for the work
“How many Lusha credits do I have left, and when do they renew?”
“Find VPs of Sales at US software companies and show me who they are before revealing anything”
“Get the work email for Ana Diaz at acme.com”
“Who is on the buying committee at acme.com, and who is the decision maker?”
“Which of these accounts raised money or started hiring fast this quarter?”
“Find companies like our best customer and score them against our Target Profile”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting Lusha behind an AI client.
No. The form asks for one thing, your Lusha API key. In Lusha, open API & connectors and click Copy API key. Every user has a key on every plan, including Free. An admin or manager can turn a person's API access off under Account Settings, Permissions.
Yes. Searches, reveals, signals and reading table rows all draw on your account's credits, the same pool the Lusha dashboard uses. lusha_get_account_usage is free and shows what is left and what each action costs. Answers also report how many requests you have left on your plan's rate limit.
Searches and prospecting answer previews with no emails or phones, so a reveal is always a separate step on people the AI has named. lusha_enrich_prospects does both in one go, but it needs a number from you, at most 25. Reveals are limited to 100 people a call, which is Lusha's own limit.
All searches, reveals, signals and scores still work, and they still spend credits, because reading is what Lusha is for. Read-only blocks creating or changing tables and webhooks, hides the webhook signing secret, and refuses a search that would also save its results to a table.
Lusha requires the email of a user on the account on every table call made with an API key, and it cannot look up who a key belongs to. Add Your Lusha email under More options when you connect, and the AI never has to ask.
Lusha gives recommendations only to a key owned by a team member, and an account-wide key gets a 403. Reconnect with a key you generated for yourself. Recommendations also need at least one Target Profile in the ICP Hub.
No. PopMCP talks to Lusha's API directly with your key, so it also covers webhooks, which Lusha's MCP server does not list. CRM export is the other way round: Lusha offers it only through its own MCP server, not its API, so it is not available here.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect Lusha in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Lusha on the consent screen. The Lusha tools are then available in that session, and no Lusha credential is stored on your machine.
Loading 77 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 35-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
A tool is something your AI calls, and there are 77 here. A trigger is something PopMCP watches for you: 3 Lusha events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Lusha.
Launch a hosted MCP endpoint for Lusha, keep tool access under control, and start testing real workflow prompts right away.