actual-mcp
Related Servers
Alternatives to actual-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that connects AI assistants to Actual Budget for budget management, enabling natural language queries, transaction creation, and spending analysis.2,479 npm76MIT
- AlicenseBqualityAmaintenanceAn MCP server that connects Actual Budget to Claude, enabling users to manage budgets, transactions, and spending insights through natural language.37452 npm20MIT
- AlicenseNot gradedqualityDmaintenanceA 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.4MIT
- FlicenseBqualityDmaintenanceA personal MCP server that gives Claude native access to YNAB budget data.46-
- FlicenseBqualityDmaintenanceMCP server that bridges Claude to Monarch Money for personal-finance analysis and lightweight edits.18-
- AlicenseAqualityDmaintenanceMCP server for Actual Budget that enables AI agents to read accounts, transactions, categories, and budgets, as well as create and update transactions and transfers.111MIT
TDQS
Scored across 17 tools
Most tools have distinct reporting purposes, but monthly-summary and cash-flow both cover income/expenses, while balance-history and net-worth both track balances over time. Several category-spending tools also overlap conceptually, though their descriptions help differentiate them.
All names use consistent kebab-case, which is predictable and readable. However, action naming is mixed: retrieval tools use a get- prefix while reporting tools omit it, creating a minor inconsistency.
17 tools is slightly heavy for a finance reporting server, but each tool covers a meaningful reporting dimension such as categories, payees, cash flow, net worth, and budget months. There is little obvious filler, though some overlap exists.
The surface is entirely read-only and covers many reporting and retrieval views, but it lacks create/update/delete operations for transactions, accounts, payees, and budgets. If the server is intentionally read-only, coverage is good; otherwise it has notable lifecycle gaps.