YNAB MCP Server
Related Servers
Alternatives to YNAB MCP Server
No user-submitted related servers found.
Related Servers
- 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
- 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.39259 npm34MIT
- 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.-
- AlicenseBqualityCmaintenanceExposes YNAB API endpoints as MCP tools, allowing AI assistants to manage budgets, accounts, transactions, and more through natural language.4495MIT
- 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.106 npmMIT
- AlicenseAqualityBmaintenanceEnables reading and writing YNAB budget data, such as listing budgets, accounts, categories, transactions, and creating or updating transactions, through natural language commands.8MIT
TDQS
Scored across 47 tools
Most tools target distinct resources (accounts, categories, transactions, etc.) with clear descriptions. However, there is some overlap between get_money_movements_for_month, list_money_movements, and similar group tools, which could cause minor confusion.
The naming uses a generally consistent verb_noun pattern (e.g., list_accounts, create_transaction), but there are inconsistencies: get_transactions_by_account uses 'get_' for a list, while similar list_ tools exist. This mixed convention slightly reduces predictability.
With 47 tools, the server is very large for typical MCP contexts. While YNAB has a broad API, the tool count feels excessive and could overwhelm agents, making selection harder.
Core CRUD operations exist for accounts, categories, transactions, scheduled transactions, and payees. Analytical tools like get_spending_by_category add value. Missing create/update for payee locations and money movement groups are minor gaps.