Related Servers

Most tools target a distinct resource+action, but there is a large family of transaction retrievers (list_transactions, get_transactions_by_account/category/month/payee, search_transactions) whose boundaries overlap and require careful reading to select correctly. Similarly, get_category vs get_category_for_month and the money-movement list/for_month pairs are close but distinguishable via their descriptions.

The dominant pattern is a clean verb_noun convention (get_plan, list_accounts, create_transaction, update_category, delete_transaction). However several tools deviate with 'by_x' / 'for_month' suffixes (get_transactions_by_account, get_category_for_month, get_money_movements_for_month) and the singular/plural bulk distinction (create_transaction vs create_transactions), which are minor inconsistencies.

At 47 tools the surface is very heavy and exceeds the threshold where counts start hurting selection. While YNAB is a broad domain, the count is inflated by consolidation opportunities (multiple transaction-fetch variants, separate money-movement/money-movement-group/month endpoints), pushing it beyond a well-scoped set.

Coverage is strong across plans, accounts, transactions (including bulk create/update and import), categories, category groups, payees, payee locations, months, scheduled transactions, and analytics (money flow, spending by category). Minor gaps exist, notably no delete_account, delete_category, delete_category_group, or explicit payee lifecycle operations.