simplefin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIMPLEFIN_ACCESS_URL | No | The permanent Access URL that embeds HTTP Basic credentials for SimpleFIN. If not provided, the server will try to read from credentials.json file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claim_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. |
| connection_statusA | Report whether an Access URL is configured (via env or a prior claim) without revealing credentials. |
| list_accountsA | List all connected accounts with current balances (no transactions). Fast — uses the balances-only mode. |
| get_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.