local-budget
Related Servers
Alternatives to local-budget
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables self-hosted personal finance management for MCP clients by connecting read-only bank accounts via SimpleFIN, syncing transactions into a local SQLite database, and exposing tools to query balances, spending, budgets, cash flow, and net worth.-
- AlicenseCqualityAmaintenanceopen-source personal finance app with a first-party MCP server. 91 HTTP tools (OAuth 2.1 + DCR) and 87 stdio tools cover transactions, budgets, accounts, portfolio analytics, FX conversion, loans, subscriptions, goals, importers, and rules. Users self-host with Docker + PostgreSQL or use the managed cloud8917AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceDeterministic bank-statement parsing for AI agents: messy CSV/OFX exports to clean, categorized ledger rows. In-memory only, no storage, no external calls, no LLM in the loop.MIT
- AlicenseAqualityAmaintenanceLocal-first personal finance MCP that aggregates bank, brokerage, credit, and loan accounts via Plaid and writes balances, holdings, and transactions to an Obsidian-style markdown vault, with access tokens stored securely in macOS Keychain.12MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with local Beancount accounting ledgers through structured tools for viewing accounts, balances, and transactions, as well as inserting/removing transactions and answering natural-language questions via BeanQuery. Provides deterministic, validated, and auditable financial data operations with offline-first functionality.1-
- AlicenseBqualityCmaintenanceEnables AI agents to manage personal finances with deterministic, grounded tools for cash-flow projection, drift detection, reconciliation, and Todoist integration. All figures trace back to a local SQLite database.55MIT
TDQS
Scored across 36 tools
Most tools have clearly distinct purposes, but a few pairs like get_category_breakdown vs budget_overview (both show per-category spend) and get_month_summary vs budget_overview (both summarize income/spend) could cause misselection. The detailed descriptions largely resolve ambiguity, but the overlap prevents a perfect score.
The naming mixes imperative verb_* forms (get_, set_, query_, render_) with noun-phrase names (top_merchants, amazon_breakdown, insights, review_queue). While readable, the pattern is not uniformly applied, making it harder to predict the tool name for a given action.
With 36 tools, the server far exceeds the 25-tool threshold for 'too many.' The feature-rich domain justifies some breadth, but many related operations (set/clear, mark/unmark) could be consolidated into single tools with parameters, reducing cognitive load.
The surface covers the core budgeting lifecycle well: income, transactions, categorization, budgets, reporting, and Amazon breakdowns. Notable gaps include no general transaction split (only Amazon charges) and conflict resolution being an external CLI dependency, but these are minor and do not block primary workflows.