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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getUserA | Returns authenticated user information |
| getPlansB | Returns plans list with summary information |
| getPlanByIdA | Returns a single plan with all related entities. This resource is effectively a full plan export. |
| getPlanSettingsByIdC | Returns settings for a plan |
| getAccountsB | Returns all accounts |
| createAccountC | Creates a new account |
| getAccountByIdB | Returns a single account |
| getCategoriesA | Returns all categories grouped by category group. Amounts (assigned, activity, available, etc.) are specific to the current plan month (UTC). |
| createCategoryC | Creates a new category |
| getCategoryByIdA | Returns a single category. Amounts (assigned, activity, available, etc.) are specific to the current plan month (UTC). |
| updateCategoryC | Update a category |
| getMonthCategoryByIdA | Returns a single category for a specific plan month. Amounts (assigned, activity, available, etc.) are specific to the current plan month (UTC). |
| updateMonthCategoryA | Update a category for a specific month. Only |
| createCategoryGroupC | Creates a new category group |
| updateCategoryGroupC | Update a category group |
| getPayeesB | Returns all payees |
| createPayeeC | Creates a new payee |
| getPayeeByIdB | Returns a single payee |
| updatePayeeD | Update a payee |
| getPayeeLocationsB | Returns all payee locations |
| getPayeeLocationByIdC | Returns a single payee location |
| getPayeeLocationsByPayeeB | Returns all payee locations for a specified payee |
| getPlanMonthsC | Returns all plan months |
| getPlanMonthB | Returns a single plan month |
| getMoneyMovementsC | Returns all money movements |
| getMoneyMovementsByMonthC | Returns all money movements for a specific month |
| getMoneyMovementGroupsC | Returns all money movement groups |
| getMoneyMovementGroupsByMonthC | Returns all money movement groups for a specific month |
| getTransactionsB | Returns plan transactions, excluding any pending transactions |
| createTransactionA | Creates a single transaction or multiple transactions. If you provide a body containing a |
| updateTransactionsC | Updates multiple transactions, by |
| importTransactionsA | Imports available transactions on all linked accounts for the given plan. Linked accounts allow transactions to be imported directly from a specified financial institution and this endpoint initiates that import. Sending a request to this endpoint is the equivalent of clicking "Import" on each account in the web application or tapping the "New Transactions" banner in the mobile applications. The response for this endpoint contains the transaction ids that have been imported. |
| getTransactionByIdC | Returns a single transaction |
| updateTransactionC | Updates a single transaction |
| deleteTransactionC | Deletes a transaction |
| getTransactionsByAccountB | Returns all transactions for a specified account, excluding any pending transactions |
| getTransactionsByCategoryB | Returns all transactions for a specified category, excluding any pending transactions |
| getTransactionsByPayeeA | Returns all transactions for a specified payee, excluding any pending transactions |
| getTransactionsByMonthB | Returns all transactions for a specified month, excluding any pending transactions |
| getScheduledTransactionsC | Returns all scheduled transactions |
| createScheduledTransactionB | Creates a single scheduled transaction (a transaction with a future date). |
| getScheduledTransactionByIdB | Returns a single scheduled transaction |
| updateScheduledTransactionC | Updates a single scheduled transaction |
| deleteScheduledTransactionB | Deletes a scheduled transaction |
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 44 tools
Each tool targets a distinct resource or operation. Even with multiple filtered transaction getters, descriptions clearly differentiate them (e.g., by account, category, month, payee). No ambiguous overlaps.
All tools follow a consistent verb_noun pattern (e.g., createAccount, getAccounts, updateCategory). Filtered getters extend this with 'By' (e.g., getTransactionsByAccount). No mixed conventions.
44 tools is significantly above the recommended 3-15 range, making the surface heavy. While YNAB has many entities, the count feels excessive for an MCP server and may overwhelm agents.
The tool set covers all major YNAB operations: CRUD for accounts, categories, payees, transactions, scheduled transactions, plans, months, and money movements. Filtered gets and import functionality ensure no dead ends.