Actual Budget MCP Server
Related Servers
Alternatives to Actual Budget MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Actual Budget for personal finance management through natural language, supporting transactions, account balances, budget tracking, spending analysis, and payment searches.397 npm1MIT
- AlicenseBqualityCmaintenanceEnables agents to read and edit budgets in Actual Budget via natural language, with a safety layer that requires confirmation for destructive actions.28535 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and agents to securely query, reconcile, analyze, and manage personal finances in Actual Budget through MCP tools and APIs.535 npmMIT
- FlicenseAqualityDmaintenanceBridges AI/LLM applications to Actual Budget, exposing budget data as MCP tools for account listing, transactions, and budget balances.4-
- AlicenseBqualityDmaintenanceEnables AI agents to interact with your Lunch Money personal finance data, providing tools for managing transactions, categories, budgets, assets, and accounts.1527 npmISC
- AlicenseAqualityCmaintenanceEnables AI assistants to connect to YNAB budgets, providing tools for accounts, transactions, categories, payees, and analytics, including search, bulk operations, and delta sync.47AGPL 3.0
TDQS
Scored across 11 tools
Every tool targets a distinct concept in the Actual budget domain: accounts, net worth, categories, transactions, spending summaries, budget month, budget averages, schedules, payees, and rules. There is slight conceptual proximity between get_spending_summary and get_budget_averages (both return spending data), and between get_payees and get_account_transfer_payee, but descriptions clearly differentiate their purposes. No tool appears to do the same thing as another.
All eleven tools follow a consistent 'get_<noun(s)>' verb_noun pattern: get_accounts, get_categories, get_transactions, get_spending_summary, get_budget_month, get_budget_averages, get_schedules, get_payees, get_rules, get_net_worth, get_account_transfer_payee. The naming convention is uniform and predictable throughout.
With 11 tools, this is a well-scoped set squarely in the optimal range. Each tool addresses a distinct read-only query a user would reasonably make about their Actual budget, and none feels redundant or trivial. The count is appropriate for the server's apparent purpose of budget querying.
The server is entirely read-only, covering queries well but offering no write operations (no 'create', 'update', 'delete' tools). Notably, the descriptions reference write tools (set_budget, set_transaction_transfer) that are not present in this set. While the domain is comprehensive on the read side, the absence of any mutation tools leaves the surface partially gap-laden if the intent is full budget management.