YNAB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YNAB_API_TOKEN | Yes | Your YNAB API 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_budgetsA | Get all budgets for the authenticated user. Returns budget names, IDs, and last modified dates. |
| get_budgetB | Get detailed information about a specific budget including accounts, categories, and settings. |
| list_accountsB | Get all accounts for a budget. Returns account names, types, balances, and status. |
| get_accountC | Get detailed information about a specific account. |
| list_categoriesB | Get all categories for a budget, grouped by category group. Includes budgeted amounts and activity. |
| get_categoryC | Get detailed information about a specific category including current month data. |
| list_transactionsC | Get transactions for a budget. Supports filtering by date, type, category, payee, and account. |
| get_transactionC | Get detailed information about a specific transaction. |
| list_payeesC | Get all payees for a budget. |
| list_scheduled_transactionsC | Get all scheduled/recurring transactions for a budget. |
| list_monthsC | Get all budget months. Returns month summaries with income, budgeted, and activity totals. |
| get_monthC | Get detailed budget information for a specific month including all category balances. |
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 12 tools
Each tool has a clearly distinct purpose targeting specific resources (e.g., accounts, budgets, categories, months, transactions, payees, scheduled transactions) with no overlap in functionality. The 'get_' tools retrieve detailed information for single items, while 'list_' tools return collections, making them easily distinguishable.
All tool names follow a consistent verb_noun pattern with 'get_' for retrieving single items and 'list_' for retrieving collections, using snake_case throughout. This predictable naming scheme enhances readability and usability for agents.
With 12 tools, the server is well-scoped for a budgeting application, covering key entities like budgets, accounts, categories, months, transactions, and payees. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain.
The tool set provides comprehensive read operations (get and list) for all major resources in YNAB, supporting core budgeting workflows. However, it lacks write operations (e.g., create, update, delete) for transactions, categories, or budgets, which could limit agent functionality for full lifecycle management.