make-cents-please
Related Servers
Alternatives to make-cents-please
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI assistants to interact with YNAB budgets, performing read-only queries by default and optional write operations like creating transactions and managing categories through natural language.45950 npm53MIT
- AlicenseAqualityCmaintenanceProvides a read-only interface to YNAB budget data, allowing AI assistants to inspect budgets, accounts, categories, transactions, and more. Includes an experimental guarded write workflow for category assignments.108 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely read and analyze local files such as CSV, JSON, and PDF from the project directory, allowing tasks like spending analysis.ISC
- AlicenseAqualityCmaintenanceEnables AI assistants to connect to YNAB budgets, providing tools for accounts, transactions, categories, payees, and analytics, including search, bulk operations, and delta sync.47AGPL 3.0
- AlicenseAqualityDmaintenanceEnables AI assistants to read, write, and manage files on the local system with security features like path restrictions and optional read-only mode.92MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to read a CashCtrl accounting ledger freely and, when explicitly configured, prepare and commit writes only after preview and confirmation, with additional opt-ins for sensitive actions.202 npm1MIT
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.