Bring Prospecting
to Cursor
Learn how to connect OmniEngage 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 OmniEngage MCP Server?
Connect your OmniEngage (Cynthia AI) account to any AI agent and take full control of your sales orchestration and prospect engagement through natural conversation. OmniEngage provides a powerful platform for automated LinkedIn and email outreach, and this integration allows you to retrieve prospect metadata, launch new research sequences, and monitor campaign performance directly from your chat interface.
What you can do
- Prospect & Lead Orchestration — List all managed prospects and retrieve detailed profile metadata programmatically to ensure your sales pipeline is always synchronized.
- Campaign & Sequence Control — Launch new outreach campaigns and trigger research sequences for prospects directly from the AI interface to drive better lead qualification.
- Engagement Intelligence — Access and monitor campaign results and retrieve detailed engagement metadata via natural language to maintain a high-fidelity interaction history.
- Webhook & Automation Control — List and oversee your configured webhooks to ensure your sales workflows are always optimized using simple AI commands.
- Operational Monitoring — Track system responses and manage prospect statuses to ensure your outreach strategy is always high-performing.
How it works
1. Subscribe to this server
2. Enter your OmniEngage API Key (Bearer Token) from your dashboard settings
3. Start managing your sales outreach from Claude, Cursor, or any MCP-compatible client
No more manual status checking in the portal. Your AI acts as a dedicated sales coordinator or lead researcher.
Who is this for?
- Sales Development Reps (SDRs) — quickly retrieve prospect summaries and monitor sequence health without switching apps.
- Growth Marketers — automate the launching of targeted outreach campaigns and track results via natural conversation.
- Account Executives — streamline the retrieval of lead metadata and monitor account engagement directly within the chat.
Built-in capabilities (12)
Verify API connectivity and account status
Pass data as a JSON string. Add a new prospect
Remove a prospect from the system
Get details for a specific campaign
Get specific prospect details
Pass data as a JSON string. Launch a new outreach campaign
List all outreach campaigns
List all outreach prospects
List all outreach sequences
List all prospect tags
List configured synchronization webhooks
Update an existing prospect
Why Cursor?
Cursor's Agent mode turns OmniEngage into an in-editor superpower. Ask Cursor to generate code using live data from OmniEngage 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
OmniEngage in Cursor
OmniEngage and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect OmniEngage 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 OmniEngage in Cursor
The OmniEngage 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
OmniEngage for Cursor
Every tool call from Cursor to the OmniEngage 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 details for a specific prospect by their ID?
Yes! Use the get_prospect tool with the Prospect ID. Your agent will respond with complete metadata for the profile, including contact info and current engagement status in seconds.
How do I find my OmniEngage API Key?
Log in to your OmniEngage account at dashboard.omniengage.co, navigate to Settings > API, and you will find your unique secret token there.
Can I launch an outreach campaign via the AI?
Absolutely. Use the launch_campaign tool. Provide the campaign data and target leads, and the agent will trigger the outreach sequence immediately.
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.