Mercury
Manage Mercury business banking accounts, cards, recipients, invoices and money movement.
About
Mercury ships in the w6w first-party pack. It declares 30 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.mercury- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Finance & Accounting
Overview
Mercury is a business banking platform. This app covers the read and write surface a workflow needs across a Mercury organization’s accounts: listing accounts and pulling statements, reading and annotating transactions, sending money to a saved recipient or transferring between an organization’s own accounts, managing recipients and expense categories, issuing and controlling virtual debit/credit cards (freeze, unfreeze, cancel), and the accounts-receivable side — customers and invoices. Organization and user reads, plus webhook management for reacting to events instead of polling, round it out.
Mercury’s own API reference documents 74 paths; the two money-movement writes this app exposes (Send Money, Create Internal Transfer) are real and can move real funds — both require an idempotency key and are flagged non-idempotent by default risk, not by vendor guarantee. Several resources are deliberately left out of a first pass — see the README’s ‘Deliberately not covered’ section, especially Mercury’s own approval-request endpoints as a safer alternative to a direct send.
Build with Mercury
Three routes to the same 30 actions. The Workflow tab is generated from Mercury's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Cancel Card
card-cancel Permanently cancel a card. Not reversible — Mercury issues a replacement rather than reinstating this one.
Freeze Card
card-freeze Freeze a card, blocking new transactions. A common automated response to suspected fraud.
List Cards
card-list List debit and credit cards, with account, status, type, and cardholder filters.
List Customers
customer-list List every accounts-receivable customer (invoice recipients this organization bills).
Get Organization
organization-get Retrieve organization details: EIN, legal business name, and DBAs.
Add Recipient
recipient-create Add a new recipient, with exactly one payment rail: ACH, domestic wire, or check.
Download Statement PDF
statement-pdf-get Download a single account statement as a base64-encoded PDF.
Get Transaction
transaction-get Retrieve a single transaction by ID, including attachments and check images.
List Transactions
transaction-list List transactions across every account, with date, status, and category filters.
Send Money to a Recipient
transaction-send Send money from a Mercury account to a saved recipient. May process immediately or require approval, per the organization's own Mercury approval policies. Moves real funds.
Update Transaction Metadata
transaction-update Set or clear a transaction's note and/or custom expense category.
Create Internal Transfer
transfer-create Transfer funds between two Mercury accounts belonging to the same organization. Moves real funds between the organization's own accounts (never to an external recipient).
Create Webhook Endpoint
webhook-create Register a new webhook endpoint. Leave event types empty to subscribe to all events.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Mercury's real ids.
{
"manifestVersion": "2",
"name": "mercury-example",
"steps": [
{
"id": "account-get",
"uses": {
"app": "io.w6w.mercury",
"action": "account-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"accountId": "<accountId>"
}
}
]
}Here are some of the things you can do
-
Get Account
readaccount-get -
List Accounts
searchaccount-list -
List Account Statements
searchaccount-statement-list -
Freeze Card
performcard-freeze -
Get Card
readcard-get
+25 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Mercury, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Mercury. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "account-get",
payload: {
accountId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action account-get --payload '{"accountId":"<value>"}'Give an AI agent Mercury — without giving it Mercury's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.mercury#account-get",
"input": {
"accountId": "<accountId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Mercury connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Mercury's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Mercury itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Mercury declares its own checks, so its health is a property of the app rather than something the host guesses at.
Mercury platform status
Component status from status.mercury.com: Support, Bill Pay & Invoicing, Integrations & API, Money Movement, Account Management, Account Access, Cards, Mercury Treasury, Account Opening, Check Deposits, and Mercury Personal. The verdict comes from the page's own status.indicator roll-up, not from any single component.