Bring Prospecting
to VS Code Copilot
Learn how to connect OmniEngage to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings OmniEngage data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
OmniEngage in VS Code Copilot
OmniEngage and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect OmniEngage to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.