Lusha in the chat with your agent.
Lusha's own MCP server, passed through per business unit. The same data as the Lusha connection, plus exporting contacts and companies into the CRM connected to Lusha.
- Vendor MCP · passed through as is
- Coverage: complete
- 18 tools (per vendor) · 15 of them make changes
Read and change.
Your agent works with exactly the permissions of the connected account. Read tools are quick to enable. Tools that change data stay off until you explicitly turn them on.
What your agent can read
- Enrichment, prospecting, buying groups, lookalikes and signals.
- Recommendations, scores, website visitors and conversations.
- Which CRMs are connected to Lusha and how much one export can handle.
What your agent can change
- Reveal contact details and maintain Lusha tables.
- Export contacts and companies into the connected CRM: Salesforce, HubSpot, Zoho, Pipedrive or SalesLoft.
Only once you enable it, per agent and per tool. If you want, a person also approves each action before it runs.
How teams use Lusha MCP.
Marketing, sales and RevOps run these as recurring routines or on request.
- 01
New contacts straight into the CRM
After revealing- Reveal the selected contacts
- Export them into the connected CRM
- Show links to the created records
ResultThe contacts are in the CRM without copy and paste. Records that already exist cost no credits.
Built-in safeguards
- Your agent can't connect a CRM to Lusha through the hub; a Lusha admin does that in the Lusha account.
- Lusha doesn't mark its tools as read-only, so the hub treats them as making changes and only enables them explicitly.
- If you want, changes only run after a person approves them, for example the team lead: in the Data Hub, in Slack or via a link. On top of that, each agent has daily and hourly limits.
- Guardrails for every agent: deletes and changes to more than 10 records need approval by default, an emergency brake kicks in on a run of deletes, and you can set your own rules per tool.
- Each connection has an access level: Read, Write or Admin. Where the vendor allows it, the Data Hub only requests the permissions for that level.
- Credentials are stored encrypted in the Data Hub, and the agent never sees them. Every call is logged.
What it can't do
- Calls use the same credits as the regular Lusha connection.
- One export handles a maximum per run depending on the CRM, for example 100 contacts for HubSpot.
Lusha decides which tools exist through its own MCP server. The hub passes on everything that server offers and refreshes the list every 24 hours.
Connect Lusha MCP to your agents.
In 30 minutes, we'll show you the Data Hub with your own tools.