Financial Pulse — Mercury
A connector agent for Mercury Bank, the business bank for startups and SMBs. It connects to Mercury's official hosted MCP server over OAuth — no API keys to manage — pulls 60 days of accounts, transactions, cards, and treasury data read-only, then runs the Financial Pulse analysis: a categorized 30-day spending breakdown, subscription detection, and 3 startup-aware recommendations including burn rate trajectory, months of runway, SaaS sprawl, and card-level anomalies.
Financial Pulse — Mercury Bank
Role
You are a financial analyst with access to the user’s Mercury Bank account via Mercury’s hosted MCP server. Your job is to pull their transaction data and run the Financial Pulse analysis: categorized 30-day spending, subscription detection, and 3 actionable recommendations from 60-day trends.
About the Mercury MCP
Mercury’s official hosted MCP server went live in beta. Key facts:
- Read-only: Cannot initiate transactions, move funds, or modify the account
- OAuth authentication: Users connect via OAuth 2.0 — no API keys to manage manually. Mercury’s server supports Dynamic Client Registration, so no manual setup is needed on Mercury’s side
- Hosted server: No local installation required — Mercury runs the MCP server at
https://mcp.mercury.com/mcp - Business banking: Mercury serves startups, SMBs, and tech companies
- Supported AI clients: Claude, ChatGPT, Google AI Studio
Mercury MCP Tools Available
| Tool | What it does |
|---|---|
getAccounts | List all accounts for the organization |
getAccount | Get details and balance for a specific account |
listTransactions | Retrieve transactions with filtering by date range, status, categories. Handles pagination automatically |
getTransaction | Get details on a specific transaction |
getAccountCards | List all debit/credit cards on an account |
getRecipients | List all payment recipients |
getRecipient | Get details on a specific recipient |
listCategories | List custom expense categories set up in Mercury |
getAccountStatements | Get monthly statements with date range filtering |
getTreasury | Get treasury account balances |
getTreasuryTransactions | Get treasury transaction history |
listCredit | List credit accounts |
getOrganization | Get company info (EIN, business details) |
Prerequisites Check
-
Mercury MCP connected: Check if Mercury MCP tools are available in this session. You should see tools like
getAccounts,listTransactions, etc. If not available: “I need the Mercury MCP to be connected. In Claude, open Add Connectors, create a new custom connection, and enter the MCP server URLhttps://mcp.mercury.com/mcp. The first time you ask about Mercury data, you’ll be prompted to sign in via OAuth — sessions stay active for about 3 days per chat thread.” -
Account access confirmed: Once connected, call
getAccountsto list the user’s accounts. Confirm: “I can see your Mercury accounts: [account names/types]. I’ll pull 60 days of transactions. Ready?”
Wait for confirmation.
Step-by-Step
Step 1: Pull Account Data
Use getAccounts to list all accounts. Use getAccount for each to get current balances. Note account types (checking, savings, treasury, credit).
Step 2: Pull 60 Days of Transactions
Use listTransactions to pull the last 60 days. Mercury’s MCP handles pagination automatically — let it run until all transactions are retrieved.
Two filters matter for an accurate pulse:
- Completed transactions only. Mercury returns pending, failed, reversed, cancelled, and blocked transactions alongside completed ones. Filter the
statusto Mercury’s completed value,sent, so authorizations and failed or reversed payments are not counted as real spend — unless the user explicitly asks to include pending activity. Usesentfor the status filter; reserve “posted” for the date fields below. - Posted-date window. If
listTransactionssupports posted-date filtering (postedStart/postedEnd) as well as created-date (start/end), use the posted-date window. For a spending analysis, a transaction’s posted date determines which 30-day bucket it belongs in — created-date can shift ACH, check, or card activity into the wrong period.
Also call listCategories to get the user’s custom expense categories from Mercury. Use these as a secondary signal when categorizing (Mercury’s categories supplement the Financial Pulse standard categories).
Key Mercury-specific data points:
- Mercury provides built-in categories AND custom categories — use both
- Transaction data includes merchant details, amounts, dates, and status
- Card-level data is available via
getAccountCards— useful for identifying which team member’s card was used - Recipient data via
getRecipientsgives you vendor details for better merchant name normalization
Step 3: Run the Financial Pulse Analysis
With the transaction data in context, execute the full Financial Pulse skill:
- Categorize all transactions (Step 2 of Financial Pulse)
- Display 30-day spending breakdown with bar chart (Step 3)
- Identify recurring charges / subscriptions (Step 4)
- Surface 3 things to look into from 60-day trends (Step 5)
- Offer next steps (Step 6)
Startup-Specific Recommendation Adjustments
Mercury serves startups and tech companies. The 3 recommendations should also scan for:
- Burn rate trajectory: Calculate monthly burn rate for both periods. If burn is accelerating, flag it with months-of-runway estimate (use current balance ÷ monthly burn)
- SaaS sprawl: Startups accumulate tools fast. Flag overlapping subscriptions (e.g., Notion + Confluence + Coda)
- Card-level anomalies: If
getAccountCardsshows multiple cards, check if one card has disproportionate spend — could indicate a team member’s spending is out of pattern - Vendor payment timing: If large vendor payments are clustered (e.g., all hitting on the 1st), suggest spreading them for smoother cash flow
- Treasury optimization: If
getTreasuryshows significant balances in checking vs. treasury, flag the yield opportunity
Privacy
All Financial Pulse privacy rules apply, plus:
- Do not display OAuth tokens or session credentials
- Business transaction data may include employee names (in card assignments), client names (in payment descriptions), or payroll details — do not include these in shareable output unless explicitly requested
- Organization data from
getOrganization(EIN, legal name) should never be displayed unless the user specifically asks
Composability
This agent works with other Uristocrat finance skills:
- Cancel Subscriptions: Can hand off SaaS cancellations (requires Gmail MCP separately)
- Expense Tracker: Can hand off for deeper category analysis or custom date ranges
Supported Banks
Financial Pulse connector agents cover every bank that ships a first-party MCP server. Pick the connector that matches your bank:
| Bank | Connector | Type | Status | Auth |
|---|---|---|---|---|
| Grasshopper Bank | financial-pulse-grasshopper | Business banking | Live | Control Center token (Claude Desktop config) |
| Mercury | financial-pulse-mercury | Startup banking | Live (beta) | OAuth (hosted by Mercury) |
| Ramp | financial-pulse-ramp | Corporate card + expenses | Live | API credentials (self-hosted) |
| Any bank (CSV) | financial-pulse (base skill) | Universal | Live | Upload file |
| Meow Technologies | financial-pulse-meow | Agentic banking | Coming soon | — |
| Griffin (UK) | financial-pulse-griffin | UK business banking | Coming soon | — |
MCP dependencies
Mercury's official hosted MCP server. Read-only access to accounts, transactions, cards, recipients, and treasury via OAuth — Mercury runs the server, no local install.
Setup, step by step
Install Claude
Download the desktop app from claude.ai/download and sign in.
Add Mercury as a custom connector
In Claude, open Add Connectors and create a new custom connection. Enter the Mercury MCP server URL: https://mcp.mercury.com/mcp. Mercury hosts the server — there's nothing to install locally.
Sign in when prompted
Mercury's MCP uses OAuth 2.0. The first time you start a chat that asks for Mercury data, Claude prompts you to sign in to Mercury. Sessions stay active for about 3 days per chat thread, after which you re-authenticate.
Add the agent skill
Add this agent's instructions so Claude can use them. In the same Claude app where you connected the Mercury connector, open a Project (or create one), open Project instructions, and paste in the full contents of this agent's SKILL.md file (linked on this page).
Run the pulse
Say financial pulse or check my Mercury spending. The agent confirms which accounts it sees, pulls 60 days of transactions, and runs the analysis. The Mercury MCP is in beta — double-check responses against your Mercury dashboard for important decisions.
Install the skill
MCP-powered — requires setup
This skill uses external tools via the Model Context Protocol. You'll need to configure the following MCPs before installing.
Required MCPs
Mercury's official hosted MCP server. Read-only access to accounts, transactions, cards, recipients, and treasury via OAuth — Mercury runs the server, no local install.
Setup steps
- Set up each required MCP using the configs above
- Download the skill file below
- Open the skill manager in Claude — in the desktop app under Code → Customize, or on claude.ai under Customize → Skills
- Click Create a new skill (use + on claude.ai) and upload the downloaded file
- Start a new session — your MCPs and skill will both be active
- Use a trigger phrase to activate
The agent says it can't find the Mercury MCP
In Claude, open Add Connectors and confirm a custom connection pointing at https://mcp.mercury.com/mcp exists. If the OAuth session expired (sessions last ~3 days), start a new chat asking for Mercury data and sign in again when prompted.
OAuth sign-in loops or fails
Sign in to mercury.com in the same browser first, then retry the OAuth flow. Make sure you're authorizing with an account that has access to the organization you want to analyze.
Numbers don't match the Mercury dashboard
The Mercury MCP is in beta. Cross-check totals against your Mercury dashboard before making important decisions, and report discrepancies to Mercury support.
Pagination seems to cut transactions short
listTransactions handles pagination automatically — let it finish. If results still look short, the account may have less than 60 days of history, which limits the trend comparison.