Mercury

What a member can do

• Read accounts, statements, cards, treasury and transactions.
• Read recipients, invoices, customers and the organisation's users.
• Request a payment to an existing recipient, or a transfer between the business's own accounts: money moves only after approval in Mercury.
• Create and edit expense categories, and update a transaction's note or category.
• It cannot create recipients, issue or manage cards, or create invoices.

Each task names the Mercury tools it may call. mercury on a task means every tool the Mercury server offers; a name such as mercury.<tool> means that tool alone. A tool the task does not name is refused, whatever the connection allows.

Who connects it

A Mercury connection acts as the Mercury account that signed in when it was connected. It can do what that account can do, and no more.

Anyone who may change tools in your enterprise can connect Mercury for a member or a team. Connecting it for the whole enterprise is for the owner, and the people the owner allows.

A connection can sit on the enterprise, a team, a member, a role or a task, and the one further down replaces the one above: task, then role, then member, then team, then enterprise. A connection on anything but a task also reaches the chat of every member it covers.

What waits for you

In a run, nothing on Mercury waits for you unless the task declares a gate on it. To approve each change before it happens, gate the tools that change something on the task. See Gates and tool scopes.

In a chat, a Mercury tool that its server does not mark as read-only asks you before it runs, unless you chose Always allow for that member and tool.

Setup

Before you connect

Mercury's MCP server is in beta. The tools offered depend on the account type and the permissions granted when signing in.

Connect it

Mercury is an Express tool, so there is no server address, key or app to set up. Work in one browser window throughout: the sign-in returns to the portal in the window you started from.

1. In the portal, open the member's page → Tools. To connect it for a team or the whole enterprise, open Tools in the sidebar.
2. Under Express, find Mercury and choose Connect. On the Tools page you are asked who uses it: one member, a team or the whole enterprise.
3. Mercury's sign-in opens. Sign in with the account the member should work as, and approve what it asks for.
4. You are back on Tools, and Mercury shows as connected.
5. Name the tools on the task, mercury for all of them or each by name.
6. Check it. Run a task that reads something from Mercury. The run page shows the call and what came back.

You can take the access back at any time: delete the connection on Tools, or remove Zero Human OS from the connected apps in your Mercury account.

A first task to try

With Mercury connected, give a member a task that uses it. For example:

Each morning, list yesterday's transactions over 1,000 dollars across our accounts, with the counterparty for each.

Start this task in the portal. It opens a conversation with your COO with the request written out. Read it, change what you like and send it. The COO asks what it still needs to know, then proposes the task for you to approve: its name, who owns it, its guardrails, the Mercury tools it may use and its instructions. Nothing is created until you approve it.