Mercury

View saved version →

---
name: mercury-mcp
description: Use Mercury's read-only MCP to answer questions about accounts, balances, transactions, spend, cash flow, runway, Treasury, cards, credit, recipients, customers, and customer invoices. Use for Mercury account and finance data requests. Do not use for payments, account changes, or vendor bills that the MCP does not expose.
---

# Mercury MCP

Answer the user's Mercury data question with the smallest complete dataset. Read `references/shared-controls.md` before any Mercury tool call.

## Select one workflow

Read only the workflow that matches the request:

- For spend, recurring charges, duplicate candidates, categories, or savings, read `references/spend-review.md`. Read only the needed sections of `references/spend-review-rules.md`.
- For liquidity, cash flow, burn, runway, or Treasury analysis, read `references/cash-runway.md`. Read only the needed sections of `references/cash-metric-definitions.md`.
- For payment counterparties, vendors, recipients, or payment-risk review, read `references/vendor-review.md`. Read only the needed sections of `references/vendor-review-rules.md`.
- For customer invoices, aging, or collection priorities, read `references/invoice-review.md`. Read only the needed sections of `references/invoice-review-rules.md`.
- For a direct lookup, use the minimum live tool calls. Do not read a workflow reference unless the lookup becomes an analysis.

Use more than one workflow only when the request spans them.

## Handle direct lookups

- For a current account balance, list accounts. Retrieve account detail only to resolve ambiguity or a missing field. Do not retrieve transactions.
- For cards, list cards for the required account. Retrieve card detail only when the answer needs a field absent from the list. Never expose a full card number.
- For credit, use credit tools. Keep credit capacity separate from deposit balance and liquidity.
- For a current Treasury balance, use Treasury balance data. Retrieve Treasury transactions only for history or transfer evidence.
- For transactions, use the exact account and period in the request. Do not broaden either scope.
- For categories, recipients, customers, or invoices, retrieve only the requested population and fields. Use detail tools only when list results lack required evidence.

## Use the live contract

Inspect the live Mercury MCP schemas in the current session. Use only available read tools and supported parameters. If the MCP does not expose required data, state the limit. Do not substitute another product or external data source unless the user requests it.

## Deliver the answer

Lead with the requested result. Include only material evidence, scope, data-quality limits, and next checks. Do not create a full finance report for a direct lookup.

Referenced files: 11