Back to integrations

Floom integration

Mercury MCP

Connect Mercury MCP to Floom so AI workers can use it when they run jobs for your company. Mercury's official MCP server (Beta) for read-only access to your Mercury business banking data — accounts, balances, transactions, cards, recipients, statements, and treasury. Cannot initiate transactions or modify account data; all mutations are blocked server-side.

Open app
Auth
OAuth (DCR)
Actions
30
Triggers
Listed

What Floom workers can do with Mercury MCP

Workers use connected tools during scheduled runs, webhook runs, or manual runs. A Mercury MCP connection can become part of a worker that researches, drafts, updates records, routes work, or prepares an approval for a teammate.

Floom keeps the worker, run history, outputs, tool calls, and approvals on the record. Side-effecting work can pause for review before anything ships.

Useful for

  • Scheduled AI workers that need Mercury MCP context.
  • Approval-gated updates before writing back to tools.
  • Running the same workflow from the dashboard, REST API, CLI, or MCP.

Categories

Model Context ProtocolProductivityDeveloper Tools