What is in the bank, what came in this week and what you paid a supplier.
Connect Mercury with a Read Only API token and Memtro reads bank accounts with available and current balances, transactions by date, account, counterparty or text with status, note and category, payment recipients with when they were last paid, the people with access and their roles, and receivable invoices with status and due date. The full account number is never read, only its last four digits. It reads on demand and there is no hourly sync. Nothing is written to Mercury.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Mercury tool, reads what it needs, and answers with the source cited.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Mercury for you. Each event can start a job, with the event as its input. Mercury signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Mercury is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What is our balance across all Mercury accounts?
What did we pay Northwind last month?
Which invoices are still unpaid, and when were they due?
What came in last week?
Who has access to the bank account?
Northwind's accounts team says an invoice is unpaid. The finance lead asks Memtro what was paid to Northwind this quarter. Memtro reads the transactions with that counterparty, with amounts, status and dates posted, and the recipient's last payment date, so the reply can quote them.
Each Monday the founder asks where the money stands. Memtro reads every account's available and current balance, the past week's incoming and outgoing transactions, and the receivable invoices still unpaid, and answers with the totals and the three largest movements.
The teams that lean on Mercury most, a question each of them asks, and what they connect beside it.
A record in Mercury is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
NetSuite
Ramp
FreeAgent
Holded
Mollie
QuickFile
Recurly
Airwallex
Maxio
Pennylane
Charity Commission (England and Wales)
Checkout.com
FCA Register
Soldo
Spendesk
Lago
Recharge
Katana
Chaser
Unleashed
Printful
Orb
Quaderno
Donorbox
Avalara AvaTax
Billy
Cin7 Core
Codat
ComplyAdvantage
inFlow Inventory
Metronome
MRPeasy
Persona
Precoro
Printify
Rydoo
Saleor
Snipcart
Swell
Veeqo
Zuora
VAT Sense
PaystackIn Mercury open the organisation menu (top left) → All Settings → Tokens; only a user allowed to manage tokens, usually an administrator, sees the option
Create an API token and choose Read Only: Read and Write tokens need an IP allowlist, which Memtro cannot use
Copy the whole token exactly as shown and paste it into Connections → Mercury in Memtro; a token left unused for a long time lapses
Ask what you paid a supplier last month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mercury tools are the same everywhere.
Not yet. Today every Mercury tool reads, searches or lists. When the connector gains actions, each is marked, granted by name per team and used only when a person asks for exactly that, so nothing is created, sent, updated or deleted until you say so.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Read Only API token. In Mercury open the organisation menu (top left) → All Settings → Tokens; only a user allowed to manage tokens, usually an administrator, sees the option.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Mercury for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time