@jbctechsolutions/mcp-mercury

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

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

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