Ometria Email Events MCP for AI. See exactly what users did with every link and open.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Ometria Email Events tracks and analyzes every interaction with your email campaigns—opens, clicks, bounces, and unsubscribes. Connects Ometria data directly to your AI agent so you can query real-time marketing performance metrics instantly.
You get a full picture of deliverability health, contact engagement history, and campaign attribution without leaving your chat window.
What your AI can do
Get event details
Gets full metadata for a single email event using its unique ID.
List email bounces
Lists all email bounce events recorded by Ometria, helping you clean up bad addresses.
List email clicks
Lists every email click event from Ometria, tracking user interest in specific links.
Retrieves full metadata and timestamps for one specific email interaction using a unique event ID.
Gathers a list of all recorded email bounce events, helping you identify invalid contacts.
Pulls a log of every click event to track which links users interacted with.
Retrieves records of email spam complaints, critical for monitoring sender reputation.
Lists a comprehensive set of all recorded email engagement events from Ometria.
Gathers data on which users opened the emails, providing basic engagement metrics.
Tracks and lists all email unsubscribe events, keeping your audience list clean and compliant.
Filters and lists engagement events associated with a single marketing campaign tag.
Retrieves the complete email interaction history for one specific customer or contact ID.
Fetches a list of the most recent general email events to track live campaign launches quickly.
Ask an AI about this
Waiting for input…
Ometria Email Events: 10 Tools for Tracking Engagement Data
Run targeted queries across all Ometria data points. Use these tools to gather specific event records, from individual opens to full contact histories.
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 Ometria Email Events on VinkiusGet Event Details
Gets full metadata for a single email event using its unique ID.
List Email Bounces
Lists all email bounce events recorded by Ometria, helping you clean up bad...
List Email Clicks
Lists every email click event from Ometria, tracking user interest in specific links.
List Email Complaints
Lists all spam complaint events to monitor your sender reputation and detect issues...
List Events By Campaign
Lists engagement events specific to a given marketing campaign tag.
List Events By Contact
Lists all recorded email events for one specific customer or contact ID.
List Email Events
Lists a comprehensive set of general email engagement events from Ometria.
List Email Opens
Lists all email open events, giving you basic metrics on who viewed the message.
List Recent Email Events
Lists the most recent general email activity across your entire account.
List Email Unsubscribes
Lists all unsubscribe events from Ometria, tracking audience opt-out trends.
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 Ometria Email Events 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 Ometria Email Events, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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 Ometria. 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 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Sifting through email performance metrics shouldn't take 20 minutes of clicks.
Today, checking campaign health means jumping between the Ometria portal and your CRM. You run a report for opens, download it. Then you open another section to check bounces, copy those contacts into a spreadsheet. It’s tedious, slow, and easy to lose context in the transfer.
With this MCP server, you just ask: 'List all email events for campaign X that bounced or failed.' The agent handles both `list_email_bounces` and `list_events_by_campaign` logic in one go. You get a single, clean list of problems, immediately.
Ometria Email Events MCP Server: Get real-time engagement data.
Manual processes require you to check campaign logs for general activity and then run a separate query just to see if the contact had any clicks. You never get a combined view of all failure points in one sitting.
Now, you ask your agent to combine `list_email_events` with `list_email_clicks`. It returns a single structured response showing both open status and click actions for the same record. The data is unified.
What your AI can actually do with this
You can connect Ometria's raw event data directly to your agent. This server lets your AI client read everything that happens in your email campaigns, giving you real-time marketing metrics without leaving your chat window. You won't have to jump between dashboards just to figure out why a campaign isn't hitting its marks.
Monitoring Campaign Health and Deliverability
You wanna check your sending health? You can use list_email_bounces to pull a list of every bounce event, so you know exactly which addresses are dead ends. For sender reputation, running list_email_complaints gives you records of spam complaints—you gotta track those fast. If you just need a general overview of everything happening across your whole account right now, use list_recent_email_events.
You can also pull a broad set of all recorded activity using list_email_events.
Tracking Core User Engagement
Want to know who opened the emails? Use list_email_opens for those basic metrics. To see what links people actually clicked, run list_email_clicks; this gives you a log of every user interaction with specific content. You can track audience drop-off by running list_email_unsubscribes, keeping your list clean and compliant. You'll also get the full picture of any general engagement events using list_events_by_campaign if you want to filter all activity tied to a single marketing tag.
Deep Diving into Specific Data Sets
You need history for one person? Use list_events_by_contact and you'll get the complete email interaction timeline for that specific customer ID. If you only care about a particular campaign, you can limit your search using list_events_by_campaign with just the tag name. For maximum detail on any single piece of activity, use get_event_details.
This pulls all the metadata and timestamps associated with one unique event ID so you know exactly what happened and when. To get a full audit trail for every single thing that’s ever clicked or bounced, you can run specialized queries: list_email_clicks tracks every link click, while list_email_bounces collects all the bad addresses.
019d75e4-5acb-70c6-a070-c7aa7495f55a 
Here's how it actually works
The bottom line is that you talk to your agent in natural language, and it pulls the complex marketing data for you.
Subscribe to this server and provide your Ometria API Key (X-Ometria-Auth).
Ask your AI client for the data. For example: 'Show me all click events from campaign X.'
The agent uses the appropriate tool, fetches the raw event logs, and formats the findings into a readable response.
Who is this actually for?
Email marketers need this. They're the ones staring at dashboards until 2 AM, manually cross-referencing open rates with click trends just to find out why a campaign stalled. If your job involves knowing if John actually opened that critical onboarding email before you call him, this is for you.
Uses list_email_clicks and list_events_by_campaign to quickly gauge campaign success or spot immediate deliverability issues without opening the marketing portal.
Runs 'Show me the email engagement history for [customer]@example.com' to verify if a customer received and opened crucial onboarding communications before their call.
Uses list_email_unsubscribes and list_email_bounces to monitor audience health, spot trends in opt-outs, and keep the contact list compliant.
What Changes When You Connect
Pinpoint the issue instantly. Instead of sifting through logs, you can ask your agent to run list_email_bounces to immediately identify which contacts need cleaning up. It's instant list hygiene.
Understand customer intent. Use list_events_by_contact to pull a single user’s entire interaction history. You see if they opened the welcome email but never clicked the pricing link, telling you exactly where to guide them next.
Measure campaign performance by tag. Running list_events_by_campaign lets you compare Campaign A vs. Campaign B side-by-side—you get all opens and clicks grouped instantly without manual filtering.
Protect your sender score. Accessing spam complaints via list_email_complaints means you don't wait for a report; the data is right there when you need to react, keeping your emails inbox-safe.
Keep track of list health. The agent handles list_email_unsubscribes, making sure you always know who opted out and why. It keeps your compliance records solid.
See it in action
Why did Campaign Alpha perform poorly?
A marketer notices low engagement on a new campaign. They ask their agent to run list_events_by_campaign. The agent quickly pulls all events, showing that while opens were high, the click rate is near zero. This tells the marketer they need to rewrite the CTA copy immediately.
Need proof of communication for a client call.
A CSM needs to confirm if a key account executive saw the product update email before their meeting. They prompt the agent with 'Show me the email engagement history for [executive]@corp.com'. The agent uses list_events_by_contact and confirms not only that it was opened, but also when.
Cleaning up a stale lead list.
A CRM manager needs to segment out inactive users. They ask the agent to combine data from list_email_bounces and list_email_unsubscribes. The agent processes both lists, giving them a clean, actionable subset of contacts for re-engagement.
Tracking live launch success.
The marketing team launches a sale email. They ask the agent to run list_recent_email_events. The real-time feed streams in activity, allowing them to see if clicks are coming through right away and spot any immediate deliverability roadblocks.
The honest tradeoffs
Running multiple reports manually
The user has to open the Ometria portal, run a report for Opens, copy the CSV. Then they have to log out and go to another section to pull Bounce data into a second sheet.
Just talk to your agent. Ask it: 'Compare opens versus bounces for Campaign X.' The agent runs list_email_opens and list_email_bounces in sequence, delivering a single, combined analysis instantly.
Guessing the right report view
The user knows they need click data but doesn't know if they should check 'Campaign Reports' or 'Contact History,' wasting 15 minutes clicking through menus.
Tell your agent what you want. Ask: 'What were the top 5 clicked links for John Doe?' The agent uses list_events_by_contact and focuses only on the clicks, skipping all unnecessary report layers.
Over-relying on dashboard averages
The marketing manager sees an average open rate of 20% but can't tell which segment or contact group is dragging it down.
Use the tools to drill down. Ask for list_events_by_contact filtered by a key negative outcome, like 'Show me all events for contacts who bounced.' This moves you from averages to actionable individuals.
When It Fits, When It Doesn't
You need this server if your core job relies on interpreting raw event streams—opens, clicks, bounces—as immediate data points. It's essential when speed and direct conversation are mandatory, like confirming a contact's activity before a meeting.
Don't use it if you just need general business intelligence (e.g., 'What were our total revenue numbers last quarter?'). For that, stick to your main BI or accounting tool. Also, don't use this just because the dashboard looks pretty; use it when you need a specific piece of data—like list_email_complaints—that is difficult to find manually.
The key difference: This gives you raw event records for immediate analysis; dashboards give aggregated numbers that hide context.
Questions you might have
How do I get an Ometria API Key? +
You can generate an API key in the Ometria settings dashboard under the API tab. This key is used for the X-Ometria-Auth header.
Can I see who marked an email as spam? +
Yes! Use the list_email_complaints tool to retrieve a list of events where users marked your emails as spam, including contact identifiers.
Does this support SMS events? +
This implementation specifically targets email engagement events (opens, clicks, bounces, etc.). For SMS tracking, please check if your Ometria instance exports these through the same events endpoint.
How do I use `list_events_by_contact` to view a single user's activity history? +
It returns all recorded events for one specific ID. You provide the contact's unique identifier, and the agent pulls every open, click, or bounce linked to that account. This gives you a complete timeline of their engagement.
What information does `get_event_details` pull when I input an event ID? +
It retrieves the full metadata log for that single incident. You'll get precise timestamps, source IP addresses, and any specific campaign identifiers tied to it. This is useful for deep forensic analysis.
If my campaign was huge, are there rate limits when calling `list_email_events`? +
Yes, like all external APIs, the server enforces standard rate limits. For massive datasets, focus on filtering by date range or running smaller batches of requests. The agent will guide you if a limit is hit.
How can I compare opens and clicks for one campaign using `list_events_by_campaign`? +
You run two separate calls: one for opens and one for clicks, both filtered by the campaign ID. Your AI client then compares the lists and tells you the ratio or total activity count.
What happens if I forget a required parameter when calling `list_email_bounces`? +
The call fails, and your agent will immediately report an error. It won't proceed until you provide the missing data—like a specific date range or campaign name. The system requires proper context to run.
We've already built the connector for Ometria Email Events. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 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.