arcade-ynab-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
}
}
} |
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| Ynab_AssignToCategoryA | Set how much is assigned to a category for a month. The difference comes from, or goes back to, Ready to Assign. |
| Ynab_CreateAccountA | Create an unlinked account with a starting balance. Checking, savings, cash and credit card accounts are on budget; other assets and liabilities are tracking accounts. |
| Ynab_CreateCategoryC | Create a category in a category group, optionally with a target (goal). |
| Ynab_CreateCategoryGroupC | Create a category group. |
| Ynab_CreatePayeeA | Create a payee. (CreateTransaction can also create a payee from payee_name.) |
| Ynab_CreateScheduledTransactionC | Schedule an upcoming or recurring transaction (bill, paycheck, transfer). |
| Ynab_CreateTransactionB | Create a transaction: a purchase, income, a transfer between accounts, or a split. |
| Ynab_DeleteScheduledTransactionA | Permanently delete a scheduled transaction. Only call this when the user has clearly asked to delete this specific scheduled transaction. |
| Ynab_DeleteTransactionA | Permanently delete one transaction. Only call this when the user has clearly asked to delete this specific transaction. |
| Ynab_FindOverspendingA | Find overspent categories (negative available) in a month and suggest where to cover them from: Ready to Assign first, then the categories with the most money available that aren't saving toward an underfunded target. Use MoveMoney to cover after the user picks. |
| Ynab_ForecastCashFlowA | Project account balances over the next N days from current balances and scheduled transactions (bills, paychecks, transfers). Reports each account's ending balance and its lowest point, to spot upcoming shortfalls. Doesn't include unscheduled spending. |
| Ynab_GetAccountB | Get a single account by ID. |
| Ynab_GetCategoryA | Get a single category's amounts and goal progress for a given month. |
| Ynab_GetMonthA | Get one plan month: Ready to Assign, age of money, income, total assigned and activity, plus every category's assigned, activity and available amounts and goal progress. Month totals cover all categories. When hidden categories are left out of the list, their combined amounts are in omitted_hidden_categories. Categories marked internal are YNAB system categories (e.g. Inflow: Ready to Assign), not budget lines. This is the best single call for "how is my budget doing this month?". |
| Ynab_GetPlanSettingsB | Get a plan's currency and date format settings. |
| Ynab_GetTransactionB | Get a single transaction by ID, including its subtransactions if it is a split. |
| Ynab_GetUserA | Get the YNAB user the current authorization belongs to. |
| Ynab_ImportTransactionsA | Ask YNAB to import new transactions from the plan's linked (direct import) accounts, like pressing "Import" in the app. Imported transactions arrive unapproved. |
| Ynab_ListAccountsB | List a plan's accounts with their type, whether they're on budget (or tracking only), and their working, cleared and uncleared balances. |
| Ynab_ListCategoriesA | List a plan's category groups and categories, with each category's assigned, activity and available amounts for the current month and its goal, if any. Use GetMonth for amounts in a different month. |
| Ynab_ListMoneyMovementsA | List money moved between categories, or between a category and Ready to Assign, newest first. Movements made together in one action share a money_movement_group_id. A missing from_category_id means the money came from Ready to Assign; a missing to_category_id means it went to Ready to Assign. Use ListCategories to resolve IDs. |
| Ynab_ListMonthsA | List monthly summaries for a plan (Ready to Assign, income, assigned, activity, age of money), newest first. Use GetMonth for category detail in a single month. |
| Ynab_ListPayeesA | List a plan's payees, sorted by name. Transfer payees (which represent transfers to another account) include the transfer_account_id. |
| Ynab_ListPlansB | List the user's YNAB plans (budgets), most recently modified first. |
| Ynab_ListScheduledTransactionsA | List upcoming and recurring scheduled transactions, soonest first, with their frequency and next date. Amounts are negative for outflows, positive for inflows. |
| Ynab_ListTransactionsA | List transactions, newest first, optionally filtered by date range and by ONE of account, category or payee. Amounts are in currency units: negative is an outflow, positive is an inflow. Split transactions include their subtransactions. When filtering by category or payee, split lines are returned as their own rows with type 'subtransaction'. |
| Ynab_MoveMoneyA | Move money between two categories, or between a category and Ready to Assign, by adjusting their assigned amounts for the month. Running it twice moves the money twice. The source must have at least the amount available. YNAB has no single "move" call, so this updates the source first and then the destination. If the second step fails, the money is left in Ready to Assign and the error says so. |
| Ynab_ReviewGoalsA | Review category targets (goals) for a month: which are underfunded and by how much, how many are on track, and whether Ready to Assign can cover the shortfall. Use AssignToCategory or MoveMoney to fund them after the user confirms. |
| Ynab_ReviewUnapprovedA | List transactions waiting for approval, each with a suggested category based on how the same payee was categorized recently. Use UpdateTransactions to approve or recategorize them after the user confirms. |
| Ynab_SummarizeSpendingA | Summarize spending over a date range, grouped by category, category group or payee. Counts budget-account transactions only. Transfers between accounts and income (inflows to Ready to Assign) are excluded; refunds reduce spending in their category. Spending is reported as a positive number. |
| Ynab_UpdateCategoryA | Rename a category, change its note or group, or set or remove its target (goal). Only the fields you pass change. (YNAB's API can't hide or unhide categories.) |
| Ynab_UpdateCategoryGroupB | Rename a category group. |
| Ynab_UpdatePayeeB | Rename a payee. The new name shows on all of its transactions. |
| Ynab_UpdateScheduledTransactionA | Change a scheduled transaction. Only the fields you pass change. |
| Ynab_UpdateTransactionsA | Apply the same changes to one or more transactions in a single request, e.g. approve a batch, recategorize, mark cleared, flag, or fix a memo. Only the fields you pass change. |
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 35 tools
Tools mostly target distinct resources and actions, with clear list/get/create/update/delete boundaries. Minor overlap exists between AssignToCategory and MoveMoney, and between FindOverspending and ReviewGoals, but descriptions clarify the distinction.
Every tool uses the same Ynab_ prefix followed by PascalCase verb-object or verb-phrase naming. The pattern is predictable and consistent across all 35 tools.
35 tools is heavy for an MCP server, exceeding the 3-15 well-scoped range by a wide margin. While YNAB is a broad domain, the surface likely creates choice overload and could be consolidated.
The tool set covers YNAB's core lifecycle for transactions, scheduled transactions, accounts, categories, category groups, payees, months, plans, money movements, goals, approvals, spending summaries, forecasting, imports, user and settings. Missing singular getters are workarounds via list operations, and unsupported deletes align with API limits.