mcp-ynab
Related Servers
Alternatives to mcp-ynab
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects AI assistants to YNAB budgets, providing over 30 tools for managing budgets, accounts, transactions, categories, and analytics with delta sync and caching.4750 PyPI38AGPL 3.0
- AlicenseAqualityBmaintenanceEnables 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.39129 npm32MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with YNAB budgets through natural language. Supports managing accounts, categories, transactions, and budget months with 21 tools for comprehensive budget operations.-
- AlicenseAqualityBmaintenanceProvides 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.102 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to help manage your You Need A Budget (YNAB) finances through comprehensive budget operations. Supports account management, transaction handling, category budgeting, split transactions, scheduled payments, and spending analytics with robust error handling and automatic retry logic.214MIT
- AlicenseBqualityCmaintenanceExposes YNAB API endpoints as MCP tools, allowing AI assistants to manage budgets, accounts, transactions, and more through natural language.4418 PyPI94MIT
TDQS
Scored across 47 tools
Most tools target distinct resources, but transaction retrieval is overloaded: list_transactions, get_transactions_by_month, and the get_transactions_by_* variants overlap heavily and could cause misselection. The descriptions clarify the filters, but an agent still has to distinguish six transaction-list entry points.
The server follows a consistent snake_case verb_noun pattern (create_account, update_category, list_payees). Minor inconsistencies exist where filtered collection retrievals use get_ instead of list_ (get_transactions_by_month vs list_transactions, get_money_movements_for_month vs list_money_movements).
47 tools is well above the threshold where a tool set becomes hard to navigate, even for a broad domain like YNAB. Many tools are justified by the API surface, but the redundant transaction and money-movement retrieval variants add unnecessary bloat.
Core lifecycles are covered: transactions, scheduled transactions, accounts, categories, category groups, payees, months, and money movements all have read and/or mutation tools. Notable minor gaps include no delete for categories/accounts/payees and no standalone list_category_groups, though these may be API limitations.