Replicas cloud agents can use Mercury to analyze account balances, transactions, card spend, invoices, statements, and treasury data. Connect the Mercury plugin, give an agent a specific finance task, and ask it to return the source records and assumptions behind its answer.
You can also connect Google Sheets or Google Docs to create finance reports, or add a repository when the work leads back to billing, invoicing, or financial operations code. Mercury's official MCP is currently in beta and read-only, so agents can inspect financial data but cannot move money or change your Mercury account.
This guide explains how to connect Mercury to Replicas and covers five workflows: cash reporting, spend analysis, invoice reconciliation, statement review, and weekly finance reporting. Replace the bracketed details with your accounts, dates, definitions, and document links.
1. Connect Mercury
- Open the Replicas environment you want to use and select its Plugins tab.
- Install Mercury and complete the Mercury OAuth flow.
- Review the access request and approve the connection.
- Start a workspace using that environment. Add Google Sheets or Google Docs if the agent should create a report outside the workspace.
Mercury data includes balances, transactions, recipients, and statements. Install it only on an environment whose members should have access to that financial information. A Global installation reaches every workspace in the organization; a team or personal environment limits the connection to that environment's workspaces.
See the plugin setup documentation for the full connection flow and Mercury's MCP security guidance for the data the connection exposes.
Start with a small read-only task:
Once the account scope looks right, move to a specific financial question.
2. Build a current cash position
A useful cash report needs a timestamp and a definition. Decide which accounts count as operating cash, whether treasury balances belong in the total, and which pending transactions should be shown separately.
If you want runway, provide the planning assumptions instead of asking the agent to invent them. Mercury can supply the current cash and historical transactions, but a runway model also needs your definition of burn and any expected cash flows outside the available history.
3. Review spend
Mercury transaction data includes details such as categories, merchants, users, and cards. Give the agent a period and a comparison so it can separate a large but expected payment from an actual change.
Review the category and merchant mappings before using the totals in a forecast. A transaction can be real and correctly recorded while still being grouped differently from your accounting chart.
4. Check invoices and incoming payments
The Mercury connection can read customers, invoices, and transactions. That makes it useful for preparing a reconciliation worklist, especially when a payment and invoice do not match cleanly.
The output is a review queue, not an accounting entry. Confirm ambiguous matches in Mercury and your accounting system before closing an invoice or changing the books.
5. Assemble a statement package
For a board meeting, audit request, or monthly close, ask the agent to inventory statements and produce an index. Define the accounts and period so missing documents are obvious.
Keep the index in a location with the same or stricter access than the underlying financial documents. Before sharing it, open a sample of the linked statements and verify the account and period.
6. Schedule a weekly finance report
Once a report format works, save the prompt as a Replicas automation. Choose the environment with Mercury and the document plugin, then schedule it after the reporting period closes.
Check the first run against Mercury before relying on the schedule. Financial reports are much easier to trust when every total has a definition, every period has exact boundaries, and every exception links back to the source record.
Start a Replicas workspace, configure the Mercury plugin, or read Mercury's MCP documentation.