Bring Contact Discovery
to Cursor
Learn how to connect ContactOut to Cursor and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the ContactOut MCP Server?
Connect your ContactOut account to any AI agent to streamline your B2B lead generation and talent acquisition workflows through natural conversation. ContactOut provides a powerful intelligence layer for discovering verified contact information and enriching professional profiles at scale.
What you can do
- Contact Discovery Orchestration — Instantly retrieve verified email addresses and direct phone numbers using LinkedIn profile URLs programmatically
- Professional Enrichment — Enrich contact and company data with detailed attributes, including job titles, locations, and social links to maintain a high-fidelity CRM
- Deep Semantic Search — Programmatically search the ContactOut database of 300M+ people using advanced filters for skills, titles, and locations
- Identity Resolution — Find the LinkedIn profile associated with a specific email address to perfectly coordinate your multichannel outreach
- Administrative Visibility — Programmatically track your credit balance and API usage statistics to coordinate your recruitment and sales budgets
How it works
1. Subscribe to this server
2. Retrieve your API Key from your ContactOut dashboard (Settings > API)
3. Start finding decision-makers and enriching your lead lists from Claude, Cursor, or any MCP client
No more manual profile scraping or guessing email formats. Your AI acts as your dedicated sales associate and recruitment coordinator.
Who is this for?
- Sales Development (SDRs) — build highly targeted outreach lists with verified contact info using natural language commands
- Technical Recruiters — search for candidates with specific skills and retrieve contact details without leaving your workspace
- Growth Marketers — automate lead enrichment and identify LinkedIn profiles from email lists through simple AI queries
Built-in capabilities (7)
Enrich company data
Enrich contact data
Find email by LinkedIn profile
Find LinkedIn profile by email
Get API usage statistics
Search for companies
Search for people
Why Cursor?
Cursor's Agent mode turns ContactOut into an in-editor superpower. Ask Cursor to generate code using live data from ContactOut and it fetches, processes, and writes. all in a single agentic loop. 7 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
ContactOut in Cursor
ContactOut and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ContactOut 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 ContactOut in Cursor
The ContactOut 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 7 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
ContactOut for Cursor
Every tool call from Cursor to the ContactOut MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my ContactOut API Key?
Log in to your account, navigate to Settings > API, and copy your unique access token.
Can I search for people by skills and location?
Yes! The search_people tool accepts a JSON object with filters like skills, location, and job_title programmatically.
How do I find an email using a LinkedIn URL?
Use the find_email_by_linkedin tool and provide the full LinkedIn profile URL to retrieve verified contact details.
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.