@jbctechsolutions/mcp-mercury
Read-only MCP server for Mercury business banking — accounts, transactions, and statements.
README
@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
| 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) |
Token handling
The Mercury API token is resolved at runtime, in this order:
MERCURY_API_TOKENenvironment variable — intended for tests/CI only- 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.