Skip to main content
Glama
hs737

MCP Server for YNAB

by hs737

Related Servers

Alternatives to MCP Server for YNAB

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      39
      223 npm
      33
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to connect to your YNAB account and read budget data, including accounts, categories, payees, and transactions, through a hosted MCP server.
      7 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      4
      MIT
    • 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
      B
      quality
      A
      maintenance
      MCP server connecting Claude to YNAB (You Need A Budget) — view budgets, categorize & split transactions, manage targets, and get spending reports through conversation.
      28
      103 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language interaction with your YNAB budget, including reviewing spending, assigning money, moving funds between categories, and updating transactions through Claude or Codex.
      MIT

    TDQS

    B3.3/5.0

    Scored across 62 tools

    Disambiguation3/5

    Several tools have overlapping purposes, such as overview_budget_snapshot vs overview_month_health for month summaries and analysis_overspent_history vs analysis_overspent_categories for overspending. The extensive descriptions and cross-references help, but an agent still faces many similar analytical tools that could cause misselection.

    Naming Consistency4/5

    Tool names use consistent snake_case with family prefixes (analysis_, overview_, triage_, bookkeeping_) and resource_list/get patterns. Minor outliers like ping and changes_since are negligible, making the naming mostly predictable across the set.

    Tool Count2/5

    With 62 tools, the server is far above the typical 3–15 range and exceeds the 25+ threshold that signals too many. While many tools serve distinct niche analyses, the sheer volume increases selection complexity and cognitive load for an agent.

    Completeness2/5

    The surface is entirely read-only; there are no create, update, or delete tools, yet descriptions reference write tools like transactions_update and reconcile_apply that are absent. This leaves core budget management workflows incomplete and creates dead ends for an agent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues