Integration

Fomo integration

Fomo is a social proof platform: events sent to it (a purchase, a sign-up, a ticket sale) are shown to website visitors as small animated notifications, formatted by a template. With this API an agent can send, list, find, read, update and delete the events of a Fomo application (one website), create templates, and read notification impressions, clicks and conversions over a date range. Event email addresses and IP addresses are accepted as inputs but not returned. Not exposed: the application settings update (its documented path is ambiguous and its answer carries the application secret) and the public Fomo Open metrics, which describe Fomo itself. API access needs a paid Fomo plan by default. Authentication is the site's auth token (Fomo dashboard, Settings, Site, near the bottom) sent in the Authorization header as Token <auth token>.

Connect Fomo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Fomo.Built from the 8 Fomo tools below, on the connection you add once.

What you can do with Fomo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Event, 6 operations

create_eventCreate eventPOSTAdds an event to the live feed for real: Fomo shows it to visitors of the website as a notification formatted by the template (event_type_id or event_type_tag). Returns the event with its rendered message.
delete_eventDelete eventDELETEDeletes an event, so it is no longer shown in the notifications. Returns a confirmation message.
find_eventFind eventGETReturns the most recently created event whose external_id or email_address equals q, for example to delete a person's events on an opt-out request. Email and IP addresses are not returned.
get_eventGet eventGETReturns one event by id: template, display fields, rendered message and click link, custom fields and timestamps. Email and IP addresses are not returned.
list_eventsList eventsGETLists the application's events, one page at a time, with meta.total_count and meta.total_pages. Raise page until it reaches meta.total_pages. Email and IP addresses are not returned.
update_eventUpdate eventPATCHChanges the fields sent on an existing event; the change shows in the live notifications. The vendor marks event_type_id required here: send the event's current value from get_event when not changing it.

Statistics, 1 operation

get_statisticsGet statisticsGETReturns notification impressions, hovers, clicks, conversions and attributed sales per day and in total for a date range.

Template, 1 operation

create_templateCreate templatePOSTCreates a template (event type) for real; its id goes into event_type_id of create_event. Templates can also be built in the Fomo dashboard, which the vendor recommends for a single site.

Use Fomo from Claude Code, Cursor or Codex

Connect Fomo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Fomo operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Fomo

Create your workspace
Sign up free. Nothing to install.
Connect Fomo once
Add your Fomo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.