YNAB MCP Server
Related Servers
Alternatives to YNAB MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceA personal MCP server that gives Claude native access to YNAB budget data.46-
- AlicenseBqualityCmaintenanceA read-only MCP server for YNAB budgeting data, enabling daily/weekly/monthly expense reviews and planning support via Claude Desktop or Claude Code.4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for interacting with YNAB (You Need A Budget). Provides tools for accessing budget data through MCP-enabled clients like Claude Desktop.4MIT
- FlicenseBqualityDmaintenanceMCP server that bridges Claude to Monarch Money for personal-finance analysis and lightweight edits.18-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude (and other MCP clients) to your Monarch Money financial data, allowing you to query accounts, transactions, and budgets, or update transactions and budget amounts through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude to interact with YNAB budgets, including listing budgets, accounts, transactions, and category spending.70 npm3MIT
TDQS
Scored across 28 tools
Most tools target distinct actions or resources, but several reporting/summary tools overlap: list_all_account_balances vs net_worth_snapshot, get_month_summary vs budget_health_check, and Ready to Assign appears in multiple tools. The descriptions do a good job differentiating them, so confusion is limited but present.
All tool names use snake_case consistently, with no mixed casing styles. However, several names are noun-phrase reports rather than verb_noun patterns (budget_health_check, net_worth_snapshot, top_payees, spending_by_category), and hello is an outlier.
At 28 tools, the set exceeds the recommended 3-15 range and crosses the 25+ heavy threshold. While many tools serve distinct purposes, several analysis/reporting tools could be consolidated, making the surface larger than necessary.
The server covers budgeting analysis, categorization, category creation, and approval workflows well, but it lacks core transaction lifecycle operations: no create_transaction, update_transaction, delete_transaction, or get_transaction by ID. Payee management and scheduled transactions are also missing, which are significant gaps for a YNAB server.