Skip to main content
Glama

Related Servers

Alternatives to ynab-mcpb

  • A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that enables AI-powered interaction with YNAB (You Need A Budget) data, allowing users to query their budgets through conversational interfaces.
    16
    35 npm
    141
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    A Model Context Protocol server that enables Claude Code to interact with You Need A Budget (YNAB) accounts, providing API access for budget management, transaction tracking, and financial insights through OAuth authentication.
    102 npm
    15
    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
  • 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.
    -
  • F
    license
    B
    quality
    Not graded
    maintenance
    Provides access to YNAB (You Need A Budget) functionality through the Model Context Protocol, allowing users to view account balances, access transaction data, and create new transactions.
    10
    -
  • 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
    16 npm
    1
    GPL 3.0

Related Servers

  • 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
    102 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    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
  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP server for personal finance management. Enables natural language expense logging, budgeting, recurring charge detection, and statement import with deterministic local calculations.
    -
  • A
    license
    Not graded
    quality
    C
    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
    A
    quality
    D
    maintenance
    A minimal and auditable MCP server that enables local AI assistants to read and manage YNAB budget data. It supports operations like listing accounts, tracking transactions, and moving money between categories while maintaining user privacy.
    9
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    An MCP server that enables LLM clients to analyze and manage YNAB budgets, accounts, categories, and transactions.
    27
    102 npm
    MIT

TDQS

A3.9/5.0

Scored across 35 tools

Disambiguation5/5

Every tool has a clearly distinct purpose targeting specific entities or actions. Tools like ynab_create_transaction, ynab_create_receipt_split_transaction, and ynab_create_scheduled_transaction handle different transaction types with no overlap, and list/get tools are uniquely scoped to budgets, accounts, categories, etc.

Naming Consistency4/5

Tool names consistently use snake_case and follow a verb_noun pattern (e.g., ynab_list_accounts, ynab_create_transaction). Minor deviations like ynab_diagnostic_info and ynab_clear_cache break the pattern slightly, but overall the convention is predictable and clear.

Tool Count3/5

With 35 tools, the server is on the heavier side. While YNAB's domain is rich, some duplication exists (e.g., single vs. batch transaction creation/update) that could be consolidated. The count feels slightly high but not extreme, and each tool serves a valid purpose.

Completeness4/5

Transaction management is fully covered (CRUD, batch, reconciliation, receipt split, comparison, export). Budgets and accounts have list/get/create but lack update/delete, which may be intentional as these are often managed in the YNAB app. Overall, the tool surface covers the core workflows well, with only minor gaps.

Maintenance

ActivitySlowing
ResponsivenessNo issues