Skip to main content
Glama
Sign In
@jbctechsolutions/mcp-mercury

@jbctechsolutions/mcp-mercury

by jbctechsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

@jbctechsolutions/mcp-mercury

License: MIT

Read-only MCP server for Mercury business banking — accounts, transactions, and statements.

A Model Context Protocol (MCP) server that exposes 6 read-only tools against the Mercury API. No payment, recipient, or any other write endpoint is implemented, by design.

Tools

Tool

Description

list_accounts

All accounts with balances, account/routing numbers, status

get_account

One account by ID

list_transactions

Transactions for an account (date range, status, search, pagination)

get_transaction

One transaction by ID

list_statements

Monthly statements (period, ending balance, PDF download URL)

download_statement_pdf

Save a statement PDF to a local path (mercury.com URLs only)

Related MCP server: Mercury MCP

Token handling

The Mercury API token is resolved at runtime, in this order:

  1. MERCURY_API_TOKEN environment variable — intended for tests/CI only

  2. 1Password CLI: op item get "Mercury API - read only" --account jbctechsolutions.1password.com --fields label=credential --reveal

The token is cached in memory only. It is never written to disk, never logged, and never included in error messages. Statement downloads refuse non-mercury.com URLs so the bearer token cannot be sent elsewhere.

Create the token in Mercury with read-only scope (Settings → API Tokens), store it in the 1Password item's credential field, and you're done — no config files.

Environment overrides

Variable

Default

Purpose

MERCURY_API_TOKEN

—

Bypass 1Password (tests/CI)

MERCURY_OP_ACCOUNT

jbctechsolutions.1password.com

1Password account

MERCURY_OP_ITEM

Mercury API - read only

1Password item name

MERCURY_API_BASE_URL

https://api.mercury.com/api/v1

API base (tests only)

Quick start

npm install
npm run build

Claude Code / Claude Desktop configuration

{
  "mcpServers": {
    "mercury": {
      "command": "node",
      "args": ["/path/to/mcp-mercury/dist/index.js"]
    }
  }
}

(Once published: npx -y @jbctechsolutions/mcp-mercury.)

The 1Password CLI must be installed and signed in to the jbctechsolutions account for token resolution to work.

Development

npm test          # vitest unit tests
npm run typecheck # tsc --noEmit
npm run build     # compile to dist/

License

MIT © JBC Tech Solutions, LLC

Available Tools

6 tools
download_statement_pdfA

Download a statement PDF (from a list_statements downloadUrl) to a local file. Only mercury.com URLs are accepted.

Inputs: output_path (required), download_url (required).

get_accountA

Get a single Mercury account by ID, including current and available balances.

Inputs: account_id (required).

get_transactionB

Get a single transaction by ID for a Mercury account.

Inputs: account_id (required), transaction_id (required).

list_accountsA

List all Mercury bank accounts with balances, account/routing numbers, and status. Read-only.

Inputs: no named parameters.

list_statementsA

List monthly statements for a Mercury account (period, ending balance, PDF download URL). Date range filters are limited to 3 months per request.

Inputs: account_id (required), end, limit, order, +1 more.

list_transactionsA

List transactions for a Mercury account, filterable by date range, status, and search term. Defaults to the last 30 days if no start date is given. Read-only.

Inputs: account_id (required), end, limit, order, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource: accounts, transactions, or statements, with no overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., list_accounts, get_transaction), making them predictable and easy to differentiate.

    Tool Count5/5

    Six tools cover the core banking operations (accounts, transactions, statements) without being too many or too few, fitting the server's read-only purpose.

    Completeness4/5

    The tool set covers listing and retrieving accounts, transactions, and statements, but lacks any write operations; however, the read-only design is intentional and well-scoped.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • Mercury MCP

      dragonkhoi
      A
      license
      Not graded
      quality
      D
      maintenance
      Simple MCP server that interfaces with the Mercury API, allowing you to talk to your Mercury banking data from any MCP client like Cursor or Claude Desktop.
      4
      MIT

    • finance-reconcile-mcp

      nalyDzzz
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for reconciling SimpleFIN bank data against Firefly III ledger, enabling audit and review workflows without mutation.
      19
      10 npm
      1
      MIT

    • Monarch Money MCP Server

      rmarji
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP and HTTP proxy server for accessing Monarch Money financial data, enabling transaction analysis, budget tracking, and cashflow insights through natural language.
      6
      MIT