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.653MIT
- 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 16 tools
Most tools are clearly distinct by resource (transactions, budgets, accounts, categories, payees, months). The only potential confusion is between ynab_get_unapproved_transactions and ynab_get_transactions with an approval filter, but the dedicated unapproved tool has a distinct purpose (pulling pending items for review).
All tools follow a consistent ynab_verb_noun pattern (e.g., ynab_list_accounts, ynab_create_transaction, ynab_delete_transaction). Minor deviation: ynab_budget_summary uses a noun phrase instead of a verb, but it's still readable and consistent with the prefix.
16 tools is slightly above the ideal 3-15 range but appropriate for a budgeting app covering transactions, budgets, accounts, categories, payees, and scheduled transactions. Each tool serves a distinct purpose and the count feels justified rather than bloated.
The tool surface covers core YNAB workflows: listing budgets/accounts/categories/payees, creating/updating/deleting/approving transactions, importing, and updating category budgets. Minor gaps include no direct way to create or update scheduled transactions, and no month-level budget reset or category rename, but agents can accomplish most tasks.