YNAB MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YNAB_PAT | Yes | YNAB Personal Access Token (PAT). Required for API access. | |
| YNAB_PLAN_ID | No | The plan UUID. Optional during initial setup to discover plans via list_plans; needed for full functionality after setup. | |
| YNAB_READ_ONLY | No | Read-only mode. Defaults to true; setting any other value fails startup. | true |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_plansB | List plan IDs and names for local setup. |
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 1 tool
With only a single tool, there is no possibility of confusion or overlap; the purpose of list_plans is entirely distinct.
The sole tool follows a clean verb_noun snake_case convention, and no inconsistent patterns exist to violate.
One tool is far too thin for a YNAB MCP server, which would naturally need to cover budgets, accounts, transactions, and categories.
Severely incomplete: it only lists plan IDs and names with no budget, account, transaction, category, or create/read operations beyond local setup.