Skip to main content
Glama
henfrydls

actual-budget-mcp

by henfrydls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to actual-budget-mcp

No user-submitted related servers found.

    Related Servers

    • actual-mcp-server

      agigante80
      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.
      1,271 npm
      66
      MIT

    • actual-budget-mcp

      Saikumarmohan
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Actual Budget that enables AI agents to read accounts, transactions, categories, and budgets, as well as create and update transactions and transfers.
      11
      1
      MIT

    • actual-mcp

      s-stefanov
      A
      license
      B
      quality
      B
      maintenance
      MCP server for integrating Actual Budget with Claude and other LLM assistants.
      17
      521 npm
      254
      TypeScript
      MIT

    • ynab-mcp-server

      Gregarrific
      F
      license
      B
      quality
      D
      maintenance
      A personal MCP server that gives Claude native access to YNAB budget data.
      46
      -

    • YNAB MCP Server

      ScottyOmega
      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
      123 npm
      MIT

    • Remote MCP Server - Expense

      MOKSH0077
      F
      license
      Not graded
      quality
      B
      maintenance
      A remote MCP server that lets users track expenses through Claude AI, supporting add, list, edit, and delete operations via natural language.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 37 tools

    Disambiguation3/5

    Most CRUD tools target distinct entities and actions, but the analytical tools overlap considerably (budget_vs_actual, get_budget_month, spending_by_category, monthly_summary, category_trends, spending_projection all surface spending data with slightly different scopes). recategorize_transaction also overlaps with update_transaction since category is likely an updatable field. Descriptions help, but an agent could easily misselect among the reporting tools.

    Naming Consistency3/5

    CRUD operations follow a clear create_/update_/delete_ pattern, but read operations are split between list_accounts and get_* tools, and analytics use noun-phrase names like budget_vs_actual, monthly_summary, and spending_by_category. The mixing is readable but not a single predictable verb_noun convention.

    Tool Count2/5

    37 tools is a heavy surface; the rule of thumb for coherence is 3-15 well-scoped tools, and here there are many overlapping analytics/reporting tools (budget_vs_actual, spending_projection, category_trends, spending_by_category, monthly_summary, balance_history) that could be consolidated. The CRUD breadth is defensible, but the total count feels bloated.

    Completeness3/5

    Core CRUD is mostly covered for accounts, categories, payees, transactions, and rules, but accounts have no update/close tool (delete_account even suggests 'prefer closing' without providing one), and rules have no update mechanism. Budgeting, sync, and reconciliation workflows are otherwise reasonably complete.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources