Fomo MCP for AI. Keep your site's social proof feed constantly active.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Fomo manages social proof notifications, letting you push real-time customer actions directly to your website's live feed. Use this MCP to programmatically create purchases, sign-ups, and other visible events instantly.
You can also design custom notification templates or clean up old records using simple conversation prompts.
What your AI can do
Create event
Pushes a new customer interaction, like a sign-up or purchase, to the live feed.
Create template
Builds a custom format for how specific social proof notifications look on your site.
Delete event
Removes a specific event from the public-facing social proof feed.
Instantly push new customer actions like sign-ups or purchases directly to your live proof feed.
Create and manage custom templates, dictating exactly how different types of social proof appear on the site.
List or retrieve specific past events to audit your feed's content and verify data accuracy.
View which third-party services are currently connected to and feeding data into Fomo.
Modify existing events for corrections or delete stale records from the live feed entirely.
Ask an AI about this
Waiting for input…
Fomo: 11 Tools for Event & Template Management
These tools give you granular control over the entire lifecycle of your social proof content, letting you create, read, update, and delete data points with precision.
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 Fomo on VinkiusCreate Event
Pushes a new customer interaction, like a sign-up or purchase, to the live feed.
Create Template
Builds a custom format for how specific social proof notifications look on your site.
Delete Event
Removes a specific event from the public-facing social proof feed.
Get Application Info
Retrieves overall attributes and context for your Fomo account setup.
Get Event
Fetches all the details about one specific event record by its ID.
Get Template
Gets the full structure and settings of a defined notification template.
List Events
Pulls a paginated list of recent social proof events that happened on your site.
List Integrations
Shows you all third-party services currently connected to the Fomo account.
List Push Messages
Displays a record of messages that were sent out through the system.
List Templates
Lists every notification template you have created in your account.
Update Event
Changes details for an event already published to the feed, like correcting a name...
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.
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 Fomo, 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 Fomo. 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 11 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Dealing with social proof notifications used to mean clicking through multiple dashboards.
Today, if a sale happens, your team has to jump between the CRM, the e-commerce backend, and finally Fomo's dashboard. You copy the customer name, you copy the product purchased, and then you manually navigate to the feed editor. It takes five clicks and half a minute just to show off one transaction.
With this MCP connected via Vinkius, that entire process vanishes. You simply tell your agent: 'Push a new event for John Smith.' Your AI client handles the data mapping and API calls in the background. The sale is live on the feed before you can finish reading this sentence.
Manage Social Proof Events with Fomo.
The biggest manual time sink was always dealing with stale or wrong data. You'd find an old event that needed changing, or a fake record you had to manually delete from the feed’s history view. It was tedious cleanup work.
Now, if that event is wrong, you just tell your agent to `update_event` or `delete_event`. The change happens immediately and correctly. You spend time running campaigns, not policing data.
What your AI can actually do with this
You need a way to show visitors that your site is busy. Fomo handles the social proof marketing—the real-time display of customer activity like purchases and sign-ups. Instead of manually pushing data, you connect this MCP through Vinkius and let your agent handle it all. You can tell your AI client to create an event for a new sale or list all active templates in one prompt.
It's about keeping the live feed accurate and current without touching any dashboards. Your agent manages everything from creating custom notification styles using create_template to cleaning up stale data with delete_event. The result is a constantly updating, believable feed that drives conversions.
019d759d-6061-7054-99a4-b2a30e5e4ccf Here's how it actually works
The bottom line is: you talk to your AI client, and it makes the changes in Fomo for you.
First, subscribe to this MCP and provide your Fomo Auth Token.
Next, tell your AI client what you want to do—for example, 'List all active notification templates' or 'Create a new purchase event for Jane Doe'.
Your agent calls the necessary tools and returns the status of the action, like confirming the event was pushed live.
Who is this actually for?
This MCP is for e-commerce marketing managers or digital operations specialists. You're the person who sees conversion rates dip because your site looks quiet. You need a reliable, automated way to keep social proof visible 24/7 without writing custom code.
Runs campaigns that depend on perceived activity and needs the agent to push new sales events immediately upon confirmation.
Manages the underlying feed integrity. They use tools like list_events and update_event to audit, correct, or delete misleading data points.
Needs to integrate social proof into client sites quickly. The agent handles the complex API calls so they just talk conversationally about what needs pushing.
What Changes When You Connect
You can trigger immediate, visible activity. Instead of waiting for a manual push, you tell the agent to use create_event and see a purchase pop up instantly.
Stop guessing how your proof looks. Use list_templates or get_template so you know exactly what format is active before you start pushing events.
Need to correct something? If an event has wrong details, don't rebuild the whole thing. Just use update_event to fix it directly on the live record.
Audit your data with precision. You can pull a list of recent activity using list_events and then grab deep metadata for one specific item using get_event.
Maintain visibility into your setup. Check out which external tools are connected via list_integrations to ensure everything is talking to each other.
See it in action
A major sale just happened, but the feed isn't updated.
The marketing manager asks their agent: 'Push a new purchase event for Sarah from Seattle using template ID 456.' The agent uses create_event and confirms it immediately appears on the site.
An old, incorrect sign-up event is cluttering the feed.
The ops specialist prompts: 'Remove that fake visitor count from yesterday.' The agent locates the record and uses delete_event, cleaning up the public view instantly.
We need to know what templates are available for a new campaign type.
The developer asks their agent: 'What notification templates do we have?' The agent runs through list_templates and provides a full rundown, saving the dev from clicking tabs.
We suspect some data is wrong and need to check every recent activity.
The manager prompts: 'List all social proof events in the last 24 hours.' The agent uses list_events, giving a paginated list so they can review everything at once.
The honest tradeoffs
Trying to push an event without knowing its format.
The user tries to write raw data directly into the feed because they don't know what structure Fomo expects for a new sale.
Incorrectly modifying existing proof.
The developer uses create_event when they really just wanted to change the location of an already published event, resulting in two conflicting records.
Manual data entry for every single interaction.
The marketing team copies and pastes details from a spreadsheet into Fomo's web interface every time a sale happens. This is slow and prone to copy-paste errors.
Ignoring necessary setup checks.
A new user starts pushing events without first checking which integrations are active, leading to incomplete or conflicting data feeds.
When It Fits, When It Doesn't
Use this MCP if your goal is automated, real-time control over the visibility and structure of social proof. You need to actively push records (create_event) or modify existing ones (update_event). Don't use it if you just want to view historical data; in that case, simple reporting tools might suffice. If you only need a static list of all events without modifying them, list_events is enough. But when the job requires managing the lifecycle—creating, updating, or deleting—this MCP is essential.
Questions you might have
How do I get a list of recent social proof events using the list_events tool? +
You ask your agent to run list_events. It returns paginated results showing records like purchases and sign-ups. This lets you audit what's visible on your site.
What is the difference between create_event and update_event? +
create_event makes a brand new record appear in the feed. update_event changes details—like correcting a misspelled name or changing a timestamp—on an event that's already live.
Do I need to run list_templates every time I push data? +
No, you don't. You only use list_templates when you want to see what formatting options are available for creating new proof events.
Can I check which systems are connected using list_integrations? +
Yes. Running list_integrations shows a comprehensive list of all third-party services currently linked to your Fomo account, helping you track data sources.
How do I verify my account status or check required settings using the get_application_info tool? +
It pulls all current metadata about your Fomo application setup. This is useful for confirming connection details, checking API limits, and ensuring your primary integration tokens are still valid.
What criteria should I use when employing the delete_event tool to remove a social proof event? +
You use it only when an event is incorrect or needs immediate removal from the live feed. You must provide the unique ID of the event you want to take down.
When should I run the create_template tool if I need a new type of notification format? +
Run this when your current social proof needs a different look or message. You define the structure and content rules for the new template before you can use it.
If I see an event listed but suspect data is wrong, how do I check its full details using get_event? +
This tool gives you all the specific metadata attached to a single event. You'll find the original source data, timestamps, and detailed user attributes for inspection.
How do I get an Auth Token for Fomo? +
You can find your API token in your Fomo dashboard under Settings > Site > API Access.
Can I use the agent to create new notification designs? +
Yes, you can use the 'create_template' tool to programmatically add new notification shells using the {{ variable }} syntax.
How do I push a purchase event to my feed via the agent? +
Use the 'create_event' tool and provide the event_type_id along with metadata like first_name, city, and title.
We've already built the connector for Fomo. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 11 tools are live and waiting.
You're up and running in seconds.
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.