Bring B2b Database
to Cursor
Learn how to connect RocketReach 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 RocketReach MCP Server?
Connect your RocketReach account to any AI agent and take full control of your B2B lead generation and contact enrichment orchestration through natural conversation. RocketReach provides a premier platform for finding verified emails and phone numbers, and this integration allows you to search for professionals, retrieve company metadata, and manage webhooks directly from your chat interface.
What you can do
- Lead & Person Orchestration — Search for professionals by name, title, or company and retrieve detailed profile metadata programmatically.
- Contact Enrichment Intelligence — Perform instant lookups for specific individuals using RocketReach IDs or LinkedIn URLs to reveal verified contact info directly from the AI interface.
- Company & Firmographic Control — Search and retrieve detailed company profiles, including domains and employee counts via natural language.
- Usage & Credit Oversight — Access real-time account profile metadata and monitor credit usage to ensure your outreach campaigns are always optimized.
- Operational Monitoring — Track system activity, manage webhooks, and retrieve billing info using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your RocketReach API Key from your account settings
3. Start enriching your sales pipeline from Claude, Cursor, or any MCP-compatible client
No more manual LinkedIn scraping or credit wasting. Your AI acts as a dedicated sales development representative or lead analyst.
Who is this for?
- SDRs & Recruiters — quickly retrieve verified contact info for target prospects without switching apps.
- Marketing Teams — automate the enrichment of lead lists and track search history via natural conversation.
- Operations Teams — streamline the retrieval of account statistics and monitor organizational credit health directly within the chat.
Built-in capabilities (12)
Check async lookup status
complete. Create a new webhook
Delete a webhook
Get account profile
Get billing details
Get credit usage stats
List search history
List configured webhooks
Get company details
Consumes 1 credit. Get verified contact info
Search for companies
Search for professionals
Why Cursor?
Cursor's Agent mode turns RocketReach into an in-editor superpower. Ask Cursor to generate code using live data from RocketReach 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
RocketReach in Cursor
RocketReach and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect RocketReach 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 RocketReach in Cursor
The RocketReach 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
RocketReach for Cursor
Every tool call from Cursor to the RocketReach 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 enrich a person's contact info using their LinkedIn URL?
Yes! Use the person_lookup tool. Provide the linkedin_url, and your agent will return the verified email addresses and phone numbers associated with that professional profile instantly.
How do I check how many RocketReach credits I have left?
Simply ask the agent to run the get_account_info or get_usage_stats action. It will retrieve your current plan details and remaining search/lookup credits.
How do I find my RocketReach API Key?
Log in to your RocketReach account, navigate to Account > API Usage & Settings, and you will find your unique secret API key there.
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.