monarch-mcp-server
monarch-mcp-server is a Python MCP server that connects an MCP-capable client (e.g., Claude Desktop/Claude Code) to the Monarch Money personal finance platform, exposing tools for accounts, transactions, budgets, cashflow, and investment holdings. It relies on an authentication setup script and persists an authenticated session locally for use by the MCP server.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README claims credentials never pass through Claude and that the session file is stored securely and encrypted, persisted to .mm/mm_session.pickle. However, there is no explicit statement about TLS requirements for upstream calls or about secret redaction/logging behavior beyond the high-level claim. No fine-grained authorization scopes are described; tool access appears tied to the local session.
⚡ Reliability
Best When
You want an MCP tool interface to Monarch Money data in a local/dev setup, and you can run a Python process that performs one-time login with MFA and keeps a persisted session on disk.
Avoid When
You need a public, internet-reachable API with centralized governance; or you cannot accept local session persistence and the operational risk of handling finance data in a local environment.
Use Cases
- • Retrieving linked Monarch Money accounts and balances
- • Fetching and filtering transaction history (date ranges, accounts, pagination)
- • Creating or updating transactions in user accounts
- • Reading budgets and spending status
- • Producing income/expense/cashflow analysis for date ranges
- • Viewing investment holdings in investment accounts
- • Refreshing account data from the upstream provider
Not For
- • Teams needing a managed hosted service with official SLAs
- • Use cases requiring fine-grained, server-enforced OAuth scopes or delegated access
- • Organizations requiring strict compliance artifacts (e.g., SOC2 reports) that are not provided here
- • Environments that cannot store or persist any authentication session artifacts locally
Interface
Authentication
Authentication is performed outside Claude (terminal-based) using a persistent session file (.mm/mm_session.pickle). The README states credentials are not passed through Claude.
Pricing
No pricing information for the MCP server itself; costs would primarily be the underlying Monarch Money service (and your local compute).
Agent Metadata
Known Gotchas
- ⚠ Session/authentication issues require running login_setup.py again; otherwise tools may return errors like 'No valid session found' / 'Authentication needed'.
- ⚠ Transaction filtering requires correct date format (YYYY-MM-DD).
- ⚠ Invalid account_id values will produce errors; use get_accounts to discover valid IDs.
- ⚠ Write operations (create/update transaction) may be non-idempotent unless the upstream API provides idempotency (not described here).
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for monarch-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.