Bring Prospecting
to Claude Desktop
Learn how to connect OmniEngage to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect OmniEngage to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
OmniEngage in Claude Desktop
OmniEngage and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect OmniEngage to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.