YNAB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YNAB_API_TOKEN | No | YNAB Personal Access Token. Can be provided via environment variable or stored in the OS keyring using 'ynab-mcp store-token'. |
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 |
|---|---|
| ynab_get_budgetsA | List all budgets available to the authenticated user. |
| ynab_get_accountsB | List all accounts in a budget with their current balances. |
| ynab_get_categoriesA | List all category groups and categories with budgeted amounts and balances. |
| ynab_move_moneyA | Move money from one category to another. |
| ynab_get_transactionsA | List recent transactions, optionally filtered by date, account, or category. |
| ynab_create_transactionA | Create a new transaction. Use negative amounts for spending, positive for income. |
| ynab_update_transactionA | Update an existing transaction. Only specified fields will be updated. |
| ynab_get_month_summaryA | Get a summary of a budget month including income, budgeted amounts, and spending. |
| ynab_get_payeesA | List all payees in the budget. |
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 9 tools
Each tool targets a distinct resource and action: creating/updating transactions, listing accounts, budgets, categories, payees, transactions, and moving money. No two tools have overlapping purposes, ensuring clear differentiation.
All tool names follow a consistent 'ynab_verb_noun' pattern in snake_case, e.g., ynab_create_transaction, ynab_get_accounts. The naming is uniformly predictable and easy to parse.
With 9 tools covering core YNAB operations, the scope is well-balanced. The count is neither too sparse nor excessive, fitting the domain of a budgeting app MCP server.
The set covers essential CRUD for transactions, reads for major entities (accounts, budgets, categories, payees), and a key operation (move_money). Missing delete transaction or create/update categories, but these are minor gaps that agents can work around.