make-cents-please
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level for stderr output. | WARNING |
| YNAB_TOOLS | No | Set to off to hide the ynab_* tools, for example when you use YNAB's own MCP server for YNAB. The Charity Record tools stay available. | on |
| CHARITYRECORD_DIR | No | Folder for Charity Record CSV files; turns on the Charity Record tools. | |
| YNAB_ACCESS_TOKEN | No | Your YNAB personal access token. Required unless YNAB_TOOLS=off. | |
| YNAB_ALLOW_WRITES | No | Set to true to enable the write tools. | false |
| YNAB_DEFAULT_PLAN_ID | No | Plan (budget) used when a tool call has no plan_id. Find ids with the ynab_list_plans tool. | last-used |
| YNAB_CACHE_TTL_SECONDS | No | How long a cached response counts as fresh. | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Access to the user's YNAB budget. Amounts are decimal strings in the plan's currency; negative amounts are outflows. Tools default to the configured plan, so plan_id is usually unnecessary. Find ids with ynab_list_accounts, ynab_list_categories, ynab_list_payees or ynab_list_plans before calling get_* tools. Prefer filters (dates, month, account, category) and small limits to keep responses short. The YNAB API allows 200 requests per hour, and responses are cached, so repeated questions are cheap.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ynab_get_userA | Get the id of the YNAB user that owns the access token. Rarely needed. |
| ynab_list_plansA | List the user's YNAB plans (budgets) with ids, currency and month range. Call this first if you need a plan_id; most tools default to the configured plan. |
| ynab_get_plan_settingsA | Get a plan's currency and date format settings. |
| ynab_get_plan_overviewA | Summarize a whole plan: account balances, net worth and how many categories, payees and transactions it has. Uses YNAB's full plan export (refreshed by delta), but returns only totals and counts. For details use the list_* tools. |
| ynab_list_accountsA | List accounts with current, cleared and uncleared balances. Use this to find account_id values for other tools. |
| ynab_get_accountB | Get one account's details and balances. |
| ynab_list_categoriesA | List budget categories with assigned (budgeted), activity and available (balance) amounts and goal info. Use this to find category_id values and to check spending against the budget. |
| ynab_get_categoryB | Get one category's assigned, activity, available and goal details, optionally for a specific month. |
| ynab_list_monthsA | List budget months (newest first) with income, assigned, activity, Ready to Assign and age of money. Good for month-over-month trends. |
| ynab_get_monthB | Get one budget month: totals (income, assigned, activity, Ready to Assign, age of money) plus per-category assigned/activity/available for that month. |
| ynab_list_payeesA | List payees (merchants, people, transfer targets). Use this to find payee_id values. |
| ynab_get_payeeC | Get one payee. |
| ynab_list_payee_locationsB | List GPS locations recorded for payees by the YNAB mobile app. |
| ynab_get_payee_locationC | Get one payee location. |
| ynab_list_transactionsA | Search transactions (newest first) with filters for dates, account, category, payee, amount and text. Returns a page of compact rows plus inflow/outflow totals for all matches. Split transactions show their splits; when filtering by category or payee, matching split lines are returned individually. |
| ynab_get_transactionA | Get one transaction in full, including ids, import details and splits. |
| ynab_list_scheduled_transactionsB | List scheduled (recurring or future) transactions, soonest first. Useful for upcoming bills. |
| ynab_get_scheduled_transactionC | Get one scheduled transaction. |
| ynab_list_money_movementsA | List money moved between categories (assigning or reassigning funds), newest first, with category names. |
| ynab_list_money_movement_groupsA | List groups of money movements (one group per assign/move action), newest first. |
| ynab_get_api_statusA | Show how many of the 200 hourly YNAB API requests have been used and cache settings. Makes no API call. |
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 21 tools
The get/list pairing per resource is clear, and descriptions explicitly delineate similar pairs (e.g. list_money_movements vs. list_money_movement_groups, get_plan_settings vs. get_plan_overview). Minor overlap remains: get_month returns per-category data that get_category can also return for a given month, and get_plan_overview partly duplicates what list_* tools provide, but the descriptions steer the agent adequately.
Every tool follows the same ynab_verb_noun pattern (ynab_list_accounts, ynab_get_transaction, ynab_get_api_status), with consistent snake_case throughout. There are no naming deviations or mixed conventions.
At 21 tools this sits in the heavy range for what is essentially a read-only budget reader, and several earn little: ynab_get_user is self-described as 'rarely needed', and the payee-location pair and ynab_get_api_status are marginal. The core resource get/list pairs are justified, but the surface could be trimmed to ~15 without loss.
The read surface is thorough — plans, accounts, categories, months, payees, locations, transactions, scheduled transactions, money movements and plan overview are all covered. However there are zero write operations (no creating/updating transactions, assigning funds, or mutating categories), which is a notable gap for a budgeting domain that the YNAB API supports.