simplefin
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@simplefin list my accounts with balances"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SimpleFIN MCP Server
A small, self-contained MCP server that exposes SimpleFIN bank data (accounts + transactions) as tools for Claude Code.
It is independent of the shared Pipedream proxy — it just adds a second MCP
server to this workspace's .mcp.json.
How SimpleFIN works
You generate a setup token (Base64) at a bridge, e.g.
https://bridge.simplefin.org/simplefin/create.The token decodes to a one-time claim URL. POSTing to it returns a permanent Access URL that embeds HTTP Basic credentials.
All data comes from
GET /accountson that Access URL.
A setup token can be claimed only once.
Related MCP server: plaid-mcp
Setup
cd C:\Users\Admin\John-Rommel\simplefin-mcp
npm installConnect (one time)
Get a setup token, then either:
npm run claim -- <YOUR_SETUP_TOKEN>or run node claim.js and paste it when prompted. This saves the Access URL to
credentials.json (mode 600, gitignored).
To test without a real bank, skip the claim step and point the server at the
public demo Access URL via env (SIMPLEFIN_ACCESS_URL, see .mcp.json below):
https://demo:demo@beta-bridge.simplefin.org/simplefinThis demo returns three sample accounts (Savings, Checking, Empty) with real
transaction data, so you can exercise list_accounts and get_transactions
immediately.
Register with Claude Code
Add this server alongside pipedream in C:\Users\Admin\John-Rommel\.mcp.json:
"simplefin": {
"command": "node",
"args": ["C:/Users/Admin/John-Rommel/simplefin-mcp/index.js"]
}If you'd rather pass credentials by env instead of credentials.json:
"simplefin": {
"command": "node",
"args": ["C:/Users/Admin/John-Rommel/simplefin-mcp/index.js"],
"env": { "SIMPLEFIN_ACCESS_URL": "https://user:pass@bridge.simplefin.org/simplefin" }
}Restart Claude Code in this folder and approve the server once.
Tools
Tool | Purpose |
| Exchange a setup token for an Access URL and save it. |
| Report whether a connection is configured (no secrets shown). |
| List accounts + balances (fast, balances-only). |
| Fetch transactions, with optional date range / pending / account filter. |
Security notes
The Access URL is as sensitive as a banking password —
credentials.jsonis written mode 600 and gitignored.All requests are HTTPS with verified certificates (Node default).
Available Tools
4 toolsclaim_setup_tokenClaim a SimpleFIN setup tokenA
Exchange a one-time Base64 setup token (from bridge.simplefin.org/simplefin/create) for a permanent Access URL and store it. Run this once to connect. Note: a setup token can only be claimed a single time.
Inputs: setupToken (required).
connection_statusCheck SimpleFIN connection statusA
Report whether an Access URL is configured (via env or a prior claim) without revealing credentials.
Inputs: no named parameters.
get_transactionsGet account transactionsA
Fetch transactions for connected accounts within an optional date range. Dates are Unix timestamps in seconds. If omitted, the bridge returns its default recent window.
Inputs: endDate, pending, startDate, accountIds.
list_accountsList accounts and balancesA
List all connected accounts with current balances (no transactions). Fast — uses the balances-only mode.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct purpose: setup, status check, account listing, and transaction retrieval. There is no overlap in functionality, making selection unambiguous.
Most tools follow a verb_noun pattern (claim_setup_token, list_accounts, get_transactions), but connection_status is a noun phrase rather than a verb-based action, breaking the pattern slightly.
Four tools cover the core lifecycle of connecting and reading financial data without unnecessary bloat. The count is well-scoped for a simple financial data server.
The tool set covers setup, status verification, account balances, and transaction history. A minor gap is the lack of a way to disconnect or update the connection, but the core workflow is complete.
Maintenance
Related MCP Connectors
Personal finance, bank account, and shared memory connector for Claude, ChatGPT, Gemini Spark & more
Read-only access to your own bank, card and brokerage accounts for Claude, ChatGPT and other AI agents: balances, transactions, spending, subscriptions, cashflow and investment holdings. It can never move money.
Ask Claude about your income and spending, and import bank statements. No bank login.
Connect AI agents to bank accounts, transactions, balances, and investments.
Related MCP Servers
- AlicenseBqualityFmaintenanceQuery bank accounts, credit cards, and transactions via Sophtron's financial data API. Works with Claude Desktop and any MCP-compatible client.101Apache 2.0
- AlicenseAqualityDmaintenanceEnables AI assistants like Claude Code to query your bank balances and transactions through the Plaid CLI. It securely wraps Plaid CLI commands as MCP tools, keeping your credentials local.6MIT
- AlicenseBqualityBmaintenanceEnables Claude to read UK bank account data—balances, transactions, cards, standing orders, direct debits, and identity—through TrueLayer's Data API, with local caching and optional live refreshes. It is read-only by design, requiring consent and never moving money.121MIT
- AlicenseNot gradedqualityBmaintenanceConnects Claude or ChatGPT to a user's own Google Sheet ledger so they can ask about their personal finances and log new spending in natural language. Exposes tools for monthly summaries, category breakdowns, top merchants, transaction listings, budget status, and expense creation.MIT