Fomo for AI agents
Fomo is a social proof marketing platform that shows real-time visitor activity notifications on websites to build trust and conversions. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Fomo.
Check event statistics
Get statistics on a Fomo event to see how a social proof notification is performing.
Create a new event notification
Create a Fomo event once a real purchase or signup happens that should be shown to visitors.
Confirm before deleting an event
Require approval before deleting an event, since it can immediately change what visitors see live.
9 Fomo actions, graded by risk.
Every Fomo action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- fomo.list_eventsList Fomo Events
- fomo.search_eventSearch Event
- fomo.get_fomo_eventGet Fomo Event
- fomo.get_statisticsGet Fomo Statistics
write
4Create and change things. Allow, or ask the user first.
- fomo.update_eventUpdate Fomo Event
- fomo.create_fomo_eventCreate Fomo Event
- fomo.update_applicationUpdate Application Settings
- fomo.create_fomo_templateCreate Fomo Template
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- fomo.delete_fomo_eventDelete Fomo Event
Fomo in three steps.
- 01Your users connect FomoThey add their Fomo api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Fomo Event” can wait for the user, and “delete Fomo Event” can be denied outright.
- 03Any agent can actYour agent calls Fomo through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('fomo', { read: 'allow', write: 'ask', // create_fomo_event destructive: 'deny', // delete_fomo_event }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Fomo connects.
Users add their Fomo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Fomo connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Fomo from any agent.
Fomo and Arc0, answered.
Can I use Fomo with Claude, ChatGPT or Cursor?
Yes. Connect Fomo to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Fomo actions you allow.
How do users connect Fomo?
Users add their Fomo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Fomo actions can my agent take?
9 in total: 4 read, 4 write and 1 destructive, such as “create Fomo Event”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Fomo?
Yes. Actions like “delete Fomo Event” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Fomo too?
Yes. The same Fomo connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Fomo into your agent.
Your users connect Fomo once, under your brand. Your agent gets 9 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan