ynab-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YNAB_API_TOKEN | Yes | YNAB Personal Access Token (required) | |
| YNAB_MCP_CACHE_TTL | No | Process-level cache TTL in seconds (optional) | 300 |
| YNAB_MCP_WEEK_START | No | Week start day (0=Monday, optional) | 0 |
| YNAB_DEFAULT_BUDGET_ID | No | Default budget ID if multiple budgets (optional) |
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_budgetsA | YNABのBudget一覧を返す。 |
| get_categoriesC | カテゴリグループとカテゴリ、当月のbudgeted/activity/balanceを返す。 |
| list_transactionsC | 取引明細を返す(深掘り用の生データ)。日付は YYYY-MM-DD 形式。 |
| get_period_summaryB | 期間(daily/weekly/monthly)の支出実績と、月次予算からの按分ペース指標を返す。 ペース指標はYNABに存在しない週次/日次予算の代わりの参考値。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_review | 今日の支出を振り返るための定型プロンプト。 |
| weekly_review | 今週の支出を振り返るための定型プロンプト。 |
| monthly_review | 今月の支出を振り返るための定型プロンプト。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct aspect: categories, period summaries, budgets list, and transactions. There is no overlap or ambiguity.
All tool names follow a clear verb_noun pattern: get_categories, get_period_summary, list_budgets, list_transactions. The verbs 'get' and 'list' are semantically appropriate and consistent with each other.
With only 4 tools, the server feels thin for the domain of personal budgeting, which typically requires CRUD operations and more read views (accounts, payees, etc.). However, it's not critically underpowered, just minimal.
The server is entirely read-only, missing essential mutation tools (create/update/delete for budgets, categories, transactions). Even among reads, there are no tools for accounts, payees, or detailed budget month data beyond categories. This will leave agents unable to perform many common YNAB tasks.