Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by calebl

Related Servers

Alternatives to YNAB MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      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
      An 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.
      8
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables Claude to interact with YNAB budgets, including listing budgets, accounts, transactions, and category spending.
      433 npm
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A 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.
      27
      18 PyPI
      2
      MIT

    TDQS

    A3.9/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and descriptions actively steer away from neighbours (list_months vs cash_flow, list_scheduled_transactions vs detect_recurring vs balance_forecast). The remaining overlap sits in the analytics cluster (spending_by_category, spending_by_payee, cash_flow, plan_summary with budgetVsActuals, list_months), which is disambiguated only by dense prose rather than sharp boundaries. ynab_apply_category_suggestions is also unclear since no companion tool produces the 'suggestions' it consumes.

    Naming Consistency4/5

    All names use snake_case with a consistent ynab_ prefix, which makes the set predictable. There is a minor drift between verb_noun names (list_months, create_transaction, move_money) and bare noun phrases (plan_summary, cash_flow, balance_forecast, spending_by_category). The deviation is cosmetic and still readable.

    Tool Count4/5

    At 22 tools the surface is on the heavy side, but YNAB is a genuinely multi-resource domain (plans, months, accounts, categories, payees, transactions, schedules, analytics) and each tool maps to a real operation. Nothing looks padded purely for the sake of count, though the analytics group could plausibly be consolidated.

    Completeness4/5

    Transaction lifecycle is fully covered (get, create, update, delete, bulk approve, import), along with budgeting operations (update_category_budget, move_money, auto_assign). Gaps are mostly where the YNAB API itself is read-only: no create/update/delete for scheduled transactions, accounts, payees, or category groups. A 'get single entity' path is also absent, but list tools plus filters cover it in practice.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data