OmniEngage MCP for AI. Manage campaigns and prospects from your chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
OmniEngage MCP Server gives your AI agent full control over multi-channel sales and marketing outreach. It connects directly to OmniEngage's API, letting you manage prospects, launch campaigns across email, SMS, and in-app messages, and track detailed engagement metrics—all from a natural conversation interface.
You retrieve prospect metadata, monitor campaign performance, and orchestrate complex workflows without logging into the web portal.
What your AI can do
Create prospect
Adds a new prospect record into the system using structured data input.
Delete prospect
Permanently removes a specified prospect from your outreach list.
Get campaign details
Retrieves performance metrics and specific information for a named campaign.
The agent checks the connection status to OmniEngage and validates account access.
You can add, retrieve details for, modify, or delete specific prospects within the system.
The agent launches new multi-channel outreach campaigns using predefined parameters.
You can pull detailed performance metrics for existing or planned campaigns.
The agent triggers specific, multi-step research sequences for prospects to advance their qualification stage.
You can list and review all configured synchronization hooks used in your sales workflows.
Ask an AI about this
Waiting for input…
OmniEngage MCP Server: 12 Tools for Outreach Ops
Use these twelve tools to manage every aspect of your sales pipeline—from listing contacts to launching full-scale marketing campaigns.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using OmniEngage on VinkiusCreate Prospect
Adds a new prospect record into the system using structured data input.
Delete Prospect
Permanently removes a specified prospect from your outreach list.
Get Campaign Details
Retrieves performance metrics and specific information for a named campaign.
Get Prospect Details
Fetches all detailed profile data and engagement history for one prospect.
Check Api Status
Verifies the connection status and operational health of your OmniEngage account.
Launch Campaign
Starts a new, multi-channel outreach campaign using structured parameters.
List Outreach Campaigns
Lists all currently configured and historical campaigns managed by the platform.
List Prospects
Retrieves a list of every prospect in your outreach database for auditing purposes.
List Sequences
Lists all existing, multi-step outreach sequences available to run.
List Tags
Retrieves a list of all segment tags applied across your prospect base.
List Webhooks
Shows a list of configured external synchronization webhooks.
Update Prospect
Modifies specific fields or status information for an existing prospect record.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The OmniEngage integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with OmniEngage, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by OmniEngage. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Status checks shouldn't require logging into three different portals.
Today, checking a prospect’s status is manual. You open the CRM for their last interaction, then switch to the marketing platform to see which sequence was triggered, and finally check the email tool just to confirm if it actually sent. It's context switching hell; you spend more time clicking than talking.
With this MCP server, your AI client handles all that cross-platform work. You simply ask: 'What's John Doe's status?' The agent runs `get_prospect_details` and pulls the complete story—interaction history, current campaign stage, and last touchpoint—and gives it to you in one go.
OmniEngage MCP Server: Run full outreach ops from chat.
The manual steps that vanish are the status updates. You don't have to copy-paste a prospect ID into Campaign A, then manually update their record in CRM B. The agent handles the entire sequence flow and state management for you.
What’s different now is control. Your AI acts as your dedicated outreach manager; it doesn't just report data—it executes complex actions like launching a campaign (`launch_campaign`) or updating metadata (`update_prospect`), giving you immediate, high-leverage action.
What your AI can actually do with this
Listen up. This server gives your agent total control over OmniEngage's sales and marketing platform, letting you handle everything from prospect intake to campaign deep-dives—all through natural conversation. You won't need to log into that clunky web portal; your AI client just takes over.
First things first: It checks the connection status with check_api_status, so you always know if your account access is good to go. Then, when it comes to prospects—the leads—you can manage their entire lifecycle right here. You'll use list_prospects to grab a full list of everyone in your database for an audit.
If you find someone new, you run create_prospect, giving the system structured data to build out a profile. Need to tweak a record? Use update_prospect. And if a lead is dead weight, you can permanently remove them with delete_prospect; it's simple.
For deep profiling, your agent executes get_prospect_details, which pulls every piece of metadata and the full engagement history for any specific prospect. You also get to see what segment tags are applied across the base by running list_tags.
When you’re ready to run outreach, it's straightforward. Your agent can list all existing campaign types using list_outreach_campaigns, or check out every sequence available via list_sequences. To start a whole new push, you trigger the action with launch_campaign, feeding in structured parameters for a multi-channel rollout across email and SMS.
You gotta know how those campaigns are doing. You can pull specific performance metrics on an existing campaign by calling get_campaign_details. Otherwise, your agent manages all the complex workflows that drive qualification: it kicks off specific research sequences to move prospects along their buying journey. These tools let you orchestrate complex lead advancement without touching a dashboard.
To keep everything running clean, the server handles automation oversight for you. You can list every configured external synchronization webhook using list_webhooks, giving you visibility into all the hooks powering your sales workflows. It’s about watching that connection and making sure those multi-step processes fire exactly when they should.
This setup lets your AI client act like a dedicated, high-powered coordinator for your entire marketing stack. You retrieve data, modify records, launch campaigns, and monitor results—all without ever leaving the chat window.
019dd130-fcc4-7244-ac12-44b7264328d9 
Here's how it actually works
The bottom line is: your AI client bypasses the graphical user interface (GUI) entirely, communicating directly with the source API via structured commands.
Subscribe to the server and input your OmniEngage API Key (Bearer Token) into the client.
Your AI agent connects using that token, authenticating with the OmniEngage platform's APIs.
The agent uses specific tool calls—like list_prospects or launch_campaign—to perform actions and return real-time data to you.
Who is this actually for?
SDRs and Account Executives who spend too much time clicking through dashboards at 2 a.m. for lead status updates. Growth Marketers tired of context switching between CRMs, marketing platforms, and spreadsheets need this. It's for anyone whose job requires monitoring multi-stage outreach campaigns without ever leaving their chat window.
Uses list_prospects to quickly check lead health and runs get_prospect_details to pull a summary of engagement history without opening the source platform.
Automates campaign launches using launch_campaign and tracks performance by asking for details on specific campaigns via get_campaign_details.
Retrieves lead metadata via get_prospect_details to prepare talking points, or uses list_tags to see how prospects are segmented before a call.
What Changes When You Connect
Stop switching apps to check status. Use list_prospects or get_prospect_details to pull full lead histories instantly, keeping you in the conversation flow.
Automate outreach without manual clicking. Running launch_campaign starts a multi-channel sequence (email/SMS) with one command, and tracking results via list_outreach_campaigns shows performance metrics immediately.
Keep your data clean and synced. Use update_prospect to modify lead status or add new metadata programmatically, ensuring the CRM record matches reality.
Gain visibility into system integrations. Running list_webhooks lets you audit every automated workflow hook without diving deep into complex settings menus.
Maintain a high-fidelity view of your sales process. You can list available sequences with list_sequences, letting your agent know exactly which follow-up paths are active.
See it in action
The Quarterly Review Prep
An AE needs to pull data on 10 accounts for a review. Instead of opening 10 separate dashboards, the agent runs list_prospects to narrow the list, then uses get_prospect_details iteratively on each one. The agent compiles all metadata and engagement history into a single, readable summary for the AE.
The Cold Lead Follow-up
A marketer identifies a high-value prospect who went silent. They use get_prospect_details to see when the last contact was made and what channel failed. The agent then uses launch_campaign to trigger a new, targeted follow-up sequence immediately.
The Pipeline Cleanup
An SDR notices several prospects marked 'Stale' in their list. They use list_prospects and then run update_prospect on the flagged leads, changing their status to 'Needs Re-qualification.' This keeps the pipeline clean without manual intervention.
Auditing Webhooks
The operations team suspects a data sync failure. They immediately run list_webhooks to see all configured synchronization points, verifying that the necessary integration hooks are active and correctly named.
The honest tradeoffs
Trying to list everything manually
A user tries to track a prospect's history by running list_prospects, seeing 50 names, then having to run separate commands for each one to see details.
Always start with targeted retrieval. Use get_prospect_details directly on the specific ID you care about. If you need a list summary first, use list_prospects, but never assume listing equals deep data.
Overwriting without checking
A developer runs update_prospect with a new JSON payload, overwriting critical engagement metrics because they didn't check the current status first.
Before writing (using update_prospect), always read the existing data first. Use get_prospect_details to pull all necessary fields so you know exactly what you're modifying and why.
Treating campaigns as static
A user assumes a campaign is still running just because they saw it in the list, but forgets to check if it expired or paused.
Never trust visual status alone. To confirm active details, use get_campaign_details and verify the dates and current state directly from the tool's output.
When It Fits, When It Doesn't
Use this server if your workflow requires constant data synchronization between a conversational AI layer and a dedicated marketing automation platform (like OmniEngage). You need to execute campaigns, manage granular prospect records, or audit complex webhooks directly from the chat interface.
Don't use it if all you need is simple reporting—if you just want to view historical reports, the native dashboard might be faster. But if you need to act on that data (launching a campaign, changing status), this is necessary.
Crucially, understand the difference between read and write operations. Use list_prospects or get_campaign_details when you just need info. Only use update_prospect, create_prospect, or launch_campaign when you are certain of the change you want to make; these tools modify live data.
Questions you might have
How do I check if my OmniEngage API key works with `check_api_status`? +
Run the check_api_status tool directly. The agent verifies connectivity and your account status instantly, confirming that all subsequent commands will work without authentication errors.
Can I use `list_prospects` to find a specific lead's metadata? +
No, list_prospects only returns basic list data. To get full profile details and engagement history for a single prospect, you must use the get_prospect_details tool.
`launch_campaign` requires me to know all the parameters ahead of time? +
Yes. You need to provide specific inputs (like JSON strings) for who the campaign targets and what content/channel it uses. The agent won't guess these details.
What if I want to change a prospect’s status? Should I use `update_prospect`? +
Yes, that's the correct tool for modifying an existing record. You must provide the unique ID and the specific fields you want to change via update_prospect.
How do I use `list_webhooks` to troubleshoot broken sales workflows? +
It lists every configured synchronization point and its status. You'll need to compare the webhook payload structure against your expected data format to find what broke.
If I run `create_prospect` with incomplete JSON data, what error should I expect? +
The system returns a specific validation failure message in the response. You must ensure required fields—like email or company name—are present before calling this function.
Does running `delete_prospect` permanently remove a record, or is there an archive? +
The prospect data deletes immediately and cannot be recovered. Always confirm the unique ID before executing this command to prevent permanent loss of history.
When using `get_campaign_details`, can I narrow the results by a specific date range? +
Yes, you pass start and end dates in the payload. This filters the reported engagement statistics so your agent only processes data from that defined time period.
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.
We've already built the connector for OmniEngage. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.