Skip to main content
Glama
s-stefanov

actual-mcp

by s-stefanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to actual-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,965 npm
      66
      MIT

    • actual-budget-mcp

      henfrydls
      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
      653 npm
      13
      MIT

    • ynab-mcp

      EthanKang1
      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

    • ynab-mcp-server

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

    • monarch-mcp

      bkichler
      F
      license
      B
      quality
      D
      maintenance
      MCP server that bridges Claude to Monarch Money for personal-finance analysis and lightweight edits.
      18
      -

    • 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
    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.2/5.0

    Scored across 17 tools

    Disambiguation3/5

    Several reporting tools overlap in purpose: spending-by-category, category-trends, budget-vs-actual, monthly-summary, and cash-flow all present spending or income data over time, which could cause an agent to select the wrong one. The get-* list tools are clearly distinct, but the analytics tools have fuzzy boundaries.

    Naming Consistency3/5

    The tool names mix two conventions: get-prefixed verbs (get-accounts, get-transactions) and descriptive hyphenated noun phrases (balance-history, net-worth, cash-flow). While all names are lowercase with hyphens and still readable, the lack of a single consistent verb_noun or noun-only pattern lowers the score.

    Tool Count4/5

    With 17 tools, the server is on the heavier side but still reasonable for a budgeting application covering accounts, transactions, categories, payees, reports, and analytics. The count feels slightly over the ideal, but most tools have a legitimate purpose.

    Completeness4/5

    The tool surface covers the main read-only aspects of a budgeting app: accounts, transactions, categories, payees, rules, reports, dashboards, and monthly budgets. Missing write operations (e.g., create transaction, update budget) and some detail views are notable gaps, but for a reporting/analytics focus the scope is largely complete.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources