# Fomo MCP > 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. ## Overview - **Category:** ecommerce - **Price:** Free - **Tags:** social-proof, conversion-optimization, real-time-notifications, customer-engagement, marketing-analytics ## Description 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. ## Tools ### 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. ### 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 or location. ## Prompt Examples **Prompt:** ``` List the last 5 social proof events in my Fomo application. ``` **Response:** ``` Retrieving events... I found 5 recent notifications, including sign-ups from New York and purchases from London. Your feed is active. ``` **Prompt:** ``` Push a new sign-up event for 'Alex' from 'San Francisco' using template ID '123'. ``` **Response:** ``` Event created! 'Alex from San Francisco' has been pushed to your live social proof feed using template ID 123. ``` **Prompt:** ``` List all active notification templates in my account. ``` **Response:** ``` Retrieving templates... I found 3 templates: 'Standard Purchase', 'New Sign-up', and 'Live Visitor Count'. Which one would you like to inspect? ``` ## Capabilities ### Push Real-Time Events Instantly push new customer actions like sign-ups or purchases directly to your live proof feed. ### Design Notification Templates Create and manage custom templates, dictating exactly how different types of social proof appear on the site. ### Review Event History List or retrieve specific past events to audit your feed's content and verify data accuracy. ### Manage Integrations View which third-party services are currently connected to and feeding data into Fomo. ### Update or Remove Records Modify existing events for corrections or delete stale records from the live feed entirely. ## Use Cases ### 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. ## Benefits - 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. ## How It Works The bottom line is: you talk to your AI client, and it makes the changes in Fomo for you. 1. First, subscribe to this MCP and provide your Fomo Auth Token. 2. 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'. 3. Your agent calls the necessary tools and returns the status of the action, like confirming the event was pushed live. ## Frequently Asked Questions **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.