Skip to main content
Glama
YNAB MCP Server

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
      9 npm
      MIT
    • A
      license
      A
      quality
      C
      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
      12 npm
      2
      GPL 3.0
    • A
      license
      A
      quality
      C
      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
      264 PyPI
      46
      AGPL 3.0

    TDQS

    B3.1/5.0

    Scored across 45 tools

    Disambiguation3/5

    Most tools have distinct targets, but there are overlapping read surfaces such as get_transactions/search_transactions/export_transactions and list_payee_locations/get_payee_locations_by_payee/get_payee_location. The detailed descriptions help, but the large set still makes misselection plausible.

    Naming Consistency4/5

    Tools mostly follow a consistent snake_case verb_noun pattern, e.g. list_accounts, get_transaction, audit_credit_card_payments. Minor deviations include meta tools like ynab_auth_status/ynab_tool_index and singular/plural variants such as money_movements vs money_movement_groups.

    Tool Count2/5

    With 45 tools, the surface is far above the typical well-scoped range and feels heavy even for a complex budgeting domain. Many specialized analytics/audit tools and by-month read variants could likely be consolidated or made optional.

    Completeness2/5

    The server covers extensive read/analysis use cases but lacks direct create/update/delete tools for core YNAB entities such as transactions, accounts, and category budgets. It also references tools like ynab_write_tool_execute and update_month_category that are not present, leaving write workflows incomplete despite preview_write_tool.

    Maintenance

    ActivityActive
    ResponsivenessSyncing