Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

Related Servers

Alternatives to YNAB MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      A personal MCP server that gives Claude native access to YNAB budget data.
      46
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      A read-only MCP server for YNAB budgeting data, enabling daily/weekly/monthly expense reviews and planning support via Claude Desktop or Claude Code.
      4
      Apache 2.0
    • 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
    • F
      license
      B
      quality
      D
      maintenance
      MCP server that bridges Claude to Monarch Money for personal-finance analysis and lightweight edits.
      18
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that connects Claude (and other MCP clients) to your Monarch Money financial data, allowing you to query accounts, transactions, and budgets, or update transactions and budget amounts through natural language.
      MIT
    • F
      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.
      4
      -

    TDQS

    B3.4/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (list_uncategorized_transactions vs list_unapproved_transactions vs search_transactions vs get_transaction), and descriptions explicitly state how they differ. A few pairs blur boundaries — net_worth_snapshot vs list_all_account_balances, budget_health_check vs get_month_summary/list_overspent_categories — but these are aggregations of other tools and are described well enough to disambiguate.

    Naming Consistency3/5

    Core CRUD tools follow a clean verb_noun snake_case pattern (list_budgets, get_transaction, create_category, categorize_transaction). However, roughly a third of the surface uses noun phrases with no verb (spending_by_category, net_worth_snapshot, top_payees, largest_transactions, budget_health_check), and bulk_suggest_categories inserts a prefix mid-pattern. Readable, but two competing conventions.

    Tool Count3/5

    Thirty tools is heavy and exceeds a comfortable working set, though the YNAB domain (budgets, accounts, transactions, categories, targets, analytics) genuinely spans a lot of ground. A handful of analytics tools (net_worth_snapshot, budget_health_check, list_all_account_balances) duplicate coverage already provided by other tools, so the set could be trimmed.

    Completeness3/5

    Transaction review, categorization, splitting, memo, approvals, categories/groups, targets, budgeting moves, and rich analytics are all covered. But basic transaction lifecycle is missing: there is no create_transaction, no delete, and no way to change a transaction's amount, date, or payee — only memo/category — nor any delete for categories, which will block common agent tasks.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data