cashcast-mcp
Related Servers
Alternatives to cashcast-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects Claude to your Google Sheets for personal finance tracking, analysis, and reporting — all through natural language.2-
- AlicenseNot gradedqualityBmaintenanceSelf-hostable remote MCP server for Lunch Money with built-in OAuth 2.1, enabling Claude to access transactions, budgets, and more on mobile, web, and desktop.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude (and other MCP clients) to your Monarch Money financial data, allowing you to query accounts, transactions, and budgets, or update transactions and budget amounts through natural language.MIT
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that connects SimpleFIN bank accounts to Claude, storing data in a local DuckDB file and providing a web dashboard.2MIT
- AlicenseAqualityBmaintenanceA personal finance tracker MCP server that imports Rocket Money data or connects banks via SimpleFIN to a local SQLite database, enabling Claude to analyze spending, subscriptions, cash flow, and debt payoff with complete privacy.1566 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to query Plaid-synced bank data stored locally in SQLite — balances, transactions, spending, cash flow, recurring charges, and liabilities — plus bounded read-only SQL and local CSV/JSON exports, all over local stdio with no hosted service or listening port.PolyForm Noncommercial 1.0.0
TDQS
Scored across 10 tools
Most tools have a clearly stated job and the descriptions actively pre-empt confusion (e.g. get_overview's yearSoFar vs get_accounts' ytd window, get_spending vs get_spend_history vs get_smoothed_spending). The weak spot is the projecting triad: get_plan, get_forecast and get_overview all surface goal landing months and net-worth projections, so an agent can reasonably hesitate over which to call for 'where am I heading'.
Eight of ten tools follow a clean get_/verb_noun snake_case pattern (get_overview, get_records, get_forecast, run_scenario). The outliers are what_would_it_take (a question-phrase rather than verb_noun) and the mildly inconsistent get_spending vs get_spend_history word order, both still readable.
Ten tools is squarely in the well-scoped range, and each one maps to a distinct question a personal-finance user actually asks (status, spending, plan, history, accounts, scenario, inverse scenario, records, forecast, smoothing). Nothing looks padded or redundant at the count level.
The analytical surface is thorough — read, drill-down, forecast, scenario and inverse-scenario all exist, with no obvious dead end for a question an agent would be asked. The gap is that the server is entirely read-only: there is no way to add or edit transactions, goals or accounts, so any workflow requiring mutation would fail.