avenir-mcp
Related Servers
Alternatives to avenir-mcp
No user-submitted related servers found.
Related Servers
- 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
- 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
- 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
- AlicenseBqualityAmaintenanceConnects 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.6260 PyPI1Apache 2.0
- AlicenseAqualityBmaintenanceEnables reading and writing YNAB budget data, such as listing budgets, accounts, categories, transactions, and creating or updating transactions, through natural language commands.8MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude and ChatGPT to securely read, categorize, and manage your YNAB budget through natural language, with a self-hosted Cloudflare Worker for private access.119 npmMIT
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes, and the descriptions explicitly disambiguate the trickiest pair (suggest_categories vs find_transactions, forecast_balance vs find_recurring_charges). The reporting cluster (get_category_balances, get_monthly_summary, get_budget_vs_actual, get_spending_trends) overlaps somewhat in scope, but each description steers to the right tool, so boundaries stay workable.
All names are snake_case with a verb_ prefix, giving a largely predictable pattern. Minor inconsistency: read operations mix get_ (get_category_balances), list_ (list_accounts) and find_ (find_transactions) for similar listing behavior.
12 tools is well within the sweet spot and each maps to a distinct task (plan discovery, reporting, transaction lookup, forecasting, categorization support). No filler tools and no topic is over-split.
The surface is read-heavy and self-referentially incomplete: suggest_categories tells the agent to 'assign with apply_categories' and list_category_groups tells it to pass a group id to create_category, but neither apply_categories nor create_category is present in this set. Read coverage (plans, accounts, categories, transactions, schedules, forecasts) is strong, but write/lifecycle operations are notably missing.