avenir-mcp
Related Servers
Alternatives to avenir-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables 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.45580 npm44MIT
- AlicenseAqualityCmaintenanceProvides 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.1010 npmMIT
- AlicenseAqualityFmaintenanceEnables users to connect their own YNAB account via OAuth and work with their budgets through natural language — reviewing plans, months, accounts, categories, payees, transactions, scheduled transactions, and money movements, plus writing changes such as creating, approving, recategorizing, or deleting transactions, assigning funds to categories, and moving money between them. It also adds read-only summaries for catching unapproved transactions and overspending, analyzing spending, tracking goal funding, and forecasting cash flow.35MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural-language interaction with your YNAB budget, including reviewing spending, assigning money, moving funds between categories, and updating transactions through Claude or Codex.MIT
- AlicenseAqualityBmaintenanceLets an AI assistant read and modify a YNAB plan, including viewing budgets, accounts, categories, and transactions, plus creating and deleting transactions. It can run locally over stdio or as a remote Cloudflare Worker connector, with optional read-only mode and category suggestions.22553 npmMIT
- AlicenseBqualityBmaintenanceConnects MCP clients such as Claude, Cursor, and Codex to a YNAB budget so users can ask about month health, cash position, overspent categories, uncategorized or unapproved transactions, subscriptions, recurring charges, and reconciliation. Read-only unless writes are explicitly enabled, in which case changes are logged with prior state and can be reverted.6239 PyPI3Apache 2.0
TDQS
Scored across 19 tools
Each tool targets a distinct analytical question (runway vs. forecast, monthly summary vs. category balances vs. budget-vs-actual vs. spending trends), and descriptions explicitly cross-reference sister tools to steer selection. There is mild inherent overlap among the several month/category reporting tools, but the boundary guidance keeps it well under control.
Uniform snake_case verb_noun pattern throughout (find_*, get_*, list_*, suggest_*), with verbs used meaningfully: list for enumeration, get for computed analysis, find for search. No camelCase or style mixing.
19 tools for a rich budgeting-analysis domain is on the heavy side but each maps to a genuinely distinct question (net worth, savings rate, age of money, debt payoff, targets, recurring charges, etc.). Nothing appears redundant enough to cut outright.
Covers the read/analysis surface thoroughly: plans, accounts, transactions, payees, schedules, categories, groups, targets, trends, forecasts, debt, net worth, savings. The main gap is the entirely read-only surface—no tools to assign budget money, categorise transactions, or create/edit records, which users must do in YNAB itself.