MercuryIntegrations · Business banking

Connect Mercury to Well

Import Mercury bank transactions and balances for real-time cash position tracking and automated matching with invoices.

What Well pulls from Mercury

Mercury feeds bank transaction, incoming wire, outgoing payment into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Mercury’s access.

From MercuryIn Well
Bank transaction
Ledger line
Incoming wire
Customer payment
Outgoing payment
Vendor expense
Balance
Cash position
Mercury
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
Mercury → Well

8 triggers from Mercury.

  • When a new transaction posts on your Mercury account

    Triggers on every debit or credit posting in a Mercury account.

    Trigger·Transaction
  • When a wire transfer arrives in Mercury

    Captures incoming wires with originator, reference, and value date.

    Trigger·Transaction
  • When a wire transfer is sent from Mercury

    Tracks outbound wires with beneficiary detail and instruction.

    Trigger·Transaction
  • When an ACH payment clears in Mercury

    Picks up cleared ACH credits and debits with the company id reference.

    Trigger·Transaction
  • When a Mercury card charge posts

    Captures debit card transactions with merchant and MCC code.

    Trigger·Transaction
  • When a check is deposited to Mercury

    Tracks check deposits with the payer, amount, and clearing date.

    Trigger·Transaction
  • When a Mercury account is read

    Pulls each Mercury account the workspace holds with its balance, currency, and routing details.

    Trigger·Account
  • When a Mercury account's payment details are read

    Resolves the account and routing numbers from the Mercury account so a payment instrument can be matched.

    Trigger·Payment method

What Well does with your Mercury connection

Connect

Connect Mercury over OAuth (MCP DCR): Well registers a client through Mercury's OAuth Dynamic Client Registration and you approve on Mercury's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings bank transaction, incoming wire, and outgoing payment in from Mercury through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Mercury entity into ledger line, customer payment, and vendor expense, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Mercury lands in the workspace as ledger line, customer payment, and vendor expense you can search, chart, and automate.

Questions Mercury unlocks

Ask in plain language. Well answers from your connected Mercury connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Mercury connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Mercury connection…

30 agent skills run on Mercury.

Each one answers a question from live Mercury data. The required ones return nothing until a source like it is connected.

Needs a source like Mercury

Runway

Know how many months of cash you have at your current burn, with both sides of the division shown.

Cash position

Know how much cash you hold right now, with the accounts counted and the ones left out both stated.

Cost structure

See where your company's money actually goes, no spreadsheets required.

Payment and invoice lookup

Find what payment settled an invoice, or catch every payment that never got one.

Burn rate

Know what you spend in an average month over a window you can see, with the months that carried no spend counted.

Cash forecast

See the settled month-end cash series and where the line goes from the last complete month.

Cash flow bridge

See how the month moved from opening cash to closing cash, with whatever does not reconcile named as its own step.

Missing supplier invoices

See which suppliers owe you paperwork, before your accountant asks.

Assign missing invoices

Put a name on every settled expense that still has no invoice.

Missing invoice sweep

Walk the whole month-end sweep in one prompt.

Close the books

Drive the month-end close from open to sent to your accounting tool.

Categorize your suppliers

Close the category gaps behind your spend before you close a month.

Board pack

The board numbers in one pass, each with its scope and its window stated.

Subscription spend

See which suppliers you pay on a schedule, what each costs a month, and how that spend moved.

Subscription actions

Cancel a subscription, ask for a better price or contest a double debit, with your bank's facts in the email.

Unposted and blocked

See what in a month has not reached the ledger, and which pile each item sits in.

Check bank and books

Check that your bank and your books match, and re-run what missed rows.

Connect Mercury in three steps

  1. 01

    Connect your Mercury account

    Authorize Well to access your Mercury account through the secure connection screen.

    • AuthOAuth (MCP DCR)
    • DiscoveryMCP .well-known
    • MCP servermcp.mercury.com/mcp
  2. 02

    Map your entities

    Confirm the connection to allow Well to retrieve your accounts, transactions, and payment means.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Verify that your Mercury transactions and transfers are appearing correctly in your Well workspace.

    • First syncstarts as soon as connect completes

Your Mercury credentials are never stored by Well, and all data retrieval is read-only. Mercury developer docs.

How Mercury stays secure with Well

Well connects to Mercury's MCP server (mcp.mercury.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Mercury secret. Tokens are scoped to the bank transaction, incoming wire, outgoing payment, and balance Mercury exposes and refreshed server-side. Reads only, Well cannot modify or delete Mercury records.

OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsmcp.mercury.com/mcp
  • Read Mercury records

    Resources the Mercury MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve bank transaction, incoming wire, outgoing payment, and balance across your stack

    Match identifiers in Mercury against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete Mercury records

    Not granted; Mercury is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store Mercury passwords or session cookies

    Authentication runs through OAuth (MCP DCR) tokens we never see.

    refused
Disconnect any time from Well settings or Mercury’s admin panel.

Frequently asked questions about Mercury and Well

How does Well retrieve my Mercury transaction data?

Well connects to your Mercury account via the Mercury MCP server to pull transactions, accounts, and payment details into your workspace.

Can I send payments or upload receipts back to Mercury from Well?

No. Well reads your transaction and transfer data to build journal entries in your Well ledger, but it does not write data, send payments, or upload receipts back to Mercury.

What specific information does Well extract from my Mercury account?

Well retrieves information about your company, accounts, transactions, payment means, and the people associated with your account.

How often does Well update my Mercury transaction history?

Well syncs with Mercury in the background to ensure your workspace has the latest transactions and transfers ready for reconciliation.

Mercury

Ready to connect Mercury?

Connect once. Every bank transaction, incoming wire, outgoing payment from Mercury becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.