YNAB MCP Server
Related Servers
Alternatives to YNAB MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enables interaction with You Need A Budget (YNAB) via their API, allowing users to manage budgets, accounts, categories, and transactions through natural language.2MIT
- 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
- AlicenseAqualityAmaintenanceAn MCP server that allows users to interact with YNAB data, enabling access to account balances, transactions, and the creation of new transactions through the Model Context Protocol.86MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects AI assistants to YNAB budgets, enabling natural language queries about finances backed by full API coverage and built-in YNAB methodology knowledge.1MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude to interact with YNAB budgets, including listing budgets, accounts, transactions, and category spending.125 npm3MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server for YNAB (You Need A Budget). Enables users to query budgets, accounts, categories, transactions, and more, as well as create, update, and delete transactions and manage scheduled transactions from any MCP client.272MIT
TDQS
Scored across 23 tools
Most tools target distinct resources, but there is real overlap: ynab_list_budgets duplicates ynab_list_plans, ynab_budget_summary duplicates ynab_plan_summary, and ynab_get_unapproved_transactions overlaps with ynab_get_transactions. The approval tools also have single and bulk variants that could be conflated, though the descriptions help.
Tool names consistently use the ynab_ prefix and mostly follow a verb_noun pattern like ynab_list_accounts and ynab_create_transaction. The mix of list/get and the plan/budget terminology shift is slightly inconsistent, but the overall convention is predictable.
23 tools is at the high end and includes duplicate legacy aliases that inflate the count. The core operations are broad enough to justify many tools, but the surface feels heavier than necessary for a focused budgeting server.
Transactions, approvals, categories, budgets, payees, accounts, and reporting are well covered, and the create/read/update/delete lifecycle for transactions is complete. Notable gaps remain for scheduled transactions, which can only be listed, and for managing categories/payees themselves.