Skip to main content
Glama
Saikumarmohan

actual-budget-mcp

Related Servers

Alternatives to actual-budget-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that connects AI assistants to Actual Budget for budget management, enabling natural language queries, transaction creation, and spending analysis.
      390 npm
      54
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for Actual Budget that enables AI agents to read and manage budget data, including accounts, transactions, categories, payees, and budget envelopes, via a long-lived engine singleton.
      AGPL 3.0
    • A
      license
      B
      quality
      A
      maintenance
      An MCP server that connects Actual Budget to Claude, enabling users to manage budgets, transactions, and spending insights through natural language.
      37
      384 npm
      6
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Bridges AI/LLM applications to Actual Budget, exposing budget data as MCP tools for account listing, transactions, and budget balances.
      4
      -
    • A
      license
      B
      quality
      B
      maintenance
      MCP server for integrating Actual Budget with Claude and other LLM assistants.
      17
      610 npm
      234
      TypeScript
      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

    TDQS

    A4.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct entity or action: listing accounts, payees, transactions, categories, category groups, and budgets are clearly separated, while add/update/delete transaction, create_transfer, and set_budget each address a unique mutation. No two tools appear to overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_* for retrieval, add/update/delete for transaction mutations, create_transfer for transfers, and set_budget for budget setting. The convention is uniform and predictable.

    Tool Count5/5

    With 11 tools, the server is well-scoped for interacting with Actual Budget. Each tool serves a clear purpose without redundancy, and the count is within the ideal 3-15 range for a domain-specific MCP server.

    Completeness5/5

    The tool surface covers the core lifecycle for transactions (list, add, update, delete, transfer) and budgets (list, set), plus all necessary reference listings (accounts, payees, categories, category groups). There are no obvious dead ends for typical budget management workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues