Bring B2b Intelligence
to Cursor
Learn how to connect Lusha to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Lusha MCP Server?
Connect your Lusha account to any AI agent and take full control of your sales prospecting and data enrichment through natural conversation. Lusha provides a premier B2B database, and this integration allows you to retrieve high-fidelity contact details (email, phone), enrich company metadata, and search for new prospects directly from your chat interface.
What you can do
- Contact & Person Enrichment — Lookup detailed contact metadata programmatically using name, company, or LinkedIn URLs to ensure your CRM is always synchronized.
- Company & Firmographic Intelligence — Access and monitor company data including industry, revenue, and headcount directly from the AI interface to qualify accounts in real-time.
- Prospecting & Search Control — Search for new contacts and companies matching your Ideal Customer Profile (ICP) via natural language to drive better sales efficiency.
- Usage & Credit Oversight — Access granular details for your credit consumption and remaining balance using simple AI commands to maintain a clear overview of your resources.
- Operational Monitoring — Track system responses and manage data ingestion to ensure your sales workflows are always optimized.
How it works
1. Subscribe to this server
2. Enter your Lusha API Key from your dashboard settings
3. Start enriching your sales data from Claude, Cursor, or any MCP-compatible client
No more manual copy-pasting from LinkedIn profiles. Your AI acts as a dedicated sales researcher or lead qualification assistant.
Who is this for?
- Sales Development Reps (SDRs) — quickly retrieve phone numbers and monitor account health without switching apps.
- Account Executives — automate the enrichment of new leads and track prospecting progress via natural conversation.
- Marketing Teams — streamline the retrieval of firmographic metadata and monitor data quality directly within the chat.
Built-in capabilities (12)
Enrich multiple companies
Enrich multiple contacts
Get firmographics
Get contact details
Check connection
Check account balance
Enrich by email
Enrich by LinkedIn
Check API usage
Search for businesses
Search for contacts
Verify API key
Why Cursor?
Cursor's Agent mode turns Lusha into an in-editor superpower. Ask Cursor to generate code using live data from Lusha and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Lusha in Cursor
Lusha and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Lusha to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Lusha in Cursor
The Lusha MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Lusha for Cursor
Every tool call from Cursor to the Lusha MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the phone number for a LinkedIn profile?
Yes! Use the get_person_by_linkedin tool. Provide the LinkedIn URL, and your agent will respond with complete metadata for the record, including verified emails and direct phone numbers in seconds.
How do I find my Lusha API Key?
Log in to your Lusha account, navigate to Settings > API & Integrations, and you will find your unique secret token there.
Does it support bulk enrichment?
Yes, use the bulk_enrich_person tool to provide an array of contacts. The AI will process the batch and return enriched metadata for all entries in a single operation.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.