Plugin · model context protocol

Groxbot + Mercury MCP

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.

How a Bot uses Mercury MCP

30 Mercury MCP tools. Connect under Plugins. The Bot still asks before anything leaves the thread.

  • Read the Mercury MCP project you name. Reproduce, summarize, or draft a patch.
  • Never merge, deploy, or change production without approval.
  • End with steps, expected vs actual, and a minimal fixture when it can.

Never without you

  • Merge, deploy, or delete a repo
  • Change production config

First message

In Mercury MCP, reproduce this bug. Steps, expected vs actual. Do not change production.

Tools a Bot can call

A sample from the Mercury MCP toolkit. The Bot calls these after you connect. Writes that would go live still wait for approval.

  • Getaccount
  • Getaccountcards
  • Getaccounts
  • Getaccountstatements
  • Getattachment
  • Getcurrentdate

Jobs that use Mercury MCP

Related integrations

FAQ

Does Groxbot have a native Mercury MCP integration?

Yes. Connect Mercury MCP under Plugins. The Bot still asks before anything leaves the thread — sending engineering included.

Can a Bot change live Mercury MCP data?

Not by default. Groxbot is talk-first: draft in the thread, grant access when it hits a wall. Live Mercury MCP writes wait for you.

Do I need a workflow builder?

No. Create a Bot, message it, grant access as needed. There isn't anything to learn — it's like bringing on a coworker.