Skip to main content
Glama
oliverames

YNAB MCP Server

by oliverames

Related Servers

Alternatives to YNAB MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to connect to YNAB budgets, providing tools for accounts, transactions, categories, payees, and analytics, including search, bulk operations, and delta sync.
      47
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Provides 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.
      10
      6 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables reading and writing YNAB budget data, such as listing budgets, accounts, categories, transactions, and creating or updating transactions, through natural language commands.
      8
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with YNAB budgets through natural language. Supports managing accounts, categories, transactions, and budget months with 21 tools for comprehensive budget operations.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with You Need A Budget (YNAB) through their API, allowing users to manage budgets, accounts, categories, transactions, payees, and scheduled transactions through natural language.
      12
      10 npm
      1
      GPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to YNAB budgets, providing over 30 tools for managing budgets, accounts, transactions, categories, and analytics with delta sync and caching.
      47
      40
      AGPL 3.0

    TDQS

    A3.5/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action pairs (list/get/search variants), and descriptions explicitly guide selection (e.g. 'prefer search_transactions to find specific rows'). The main mild risk is the cluster of aggregate reporting tools (income/spending summary, budget health, recurring detection, audits) and get_transactions/search_transactions/export_transactions, but each has a distinct output or purpose.

    Naming Consistency4/5

    The dominant pattern is verb_noun (list_budgets, get_category, search_payees, export_transactions, audit_credit_card_payments, detect_recurring_charges). Minor deviations include get_transactions instead of list_transactions, get_payee_locations_by_payee, and the ynab_tool_* meta tools, but these are readable and mostly predictable.

    Tool Count2/5

    With 39 tools, the set feels heavy, especially since several are near-duplicate scoped variants (four money-movement tools, four payee-location tools, plus search and export variants). While the YNAB domain is broad, this count exceeds a comfortable size and many tools could be consolidated without losing clarity.

    Completeness2/5

    The server is heavily read-only: it covers lookup, search, audit, and reporting well, but there are no actual transaction/category/account write tools despite mentions of write capability and references to actions like update_month_category and approval. Core lifecycle operations for editing transactions, approving entries, or updating budgets are missing, which leaves significant workflow gaps.

    Maintenance

    ActivityActive
    ResponsivenessResponsive