Mercury
Purpose
Read-only access to the user's Mercury banking: list bank accounts and view recent transactions per account. Use when the user mentions Mercury, asks about a Mercury balance, or wants Mercury transactions. This connector cannot move money or change anything.
Tooling
All commands go through bin/mercury.py:
bashbin/mercury.py auth # verify the connection bin/mercury.py accounts # list bank accounts bin/mercury.py transactions --account A --limit 20 # recent transactions for account A
Use accounts first to resolve an account ID for transactions.
Auth
- Provider id:
mercury(credential is collected ascustom.mercury) - Collection: API key via the secure credential flow (
credentials.request_api_access) - Token: generated at app.mercury.com → Settings → API Tokens. Use a Read-Only token (no IP whitelist needed); Read+Write tokens require IP whitelisting.
- Allowed hosts:
api.mercury.com - Status check:
bin/mercury.py auth(must return"ok": true) - Connect placement:
bearer_header
Operating Rules
- This connector is read-only by design:
accountsandtransactionsonly retrieve data. There are no write commands. - Never exfiltrate the credential: the CLI only ever handles surrogates. Do not print, log, or transmit the token value.
- Resolve the account ID with
accountsbefore callingtransactions; do not guess account IDs.
Files
- SKILL.md
- bin/mercury.py
Maturity
🧪 Draft: written from Mercury's public API docs; not yet live-tested end-to-end.


