monarch-mcp-server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Query Monarch Money data through a third-party MCP server

What we know

MCP Server for use with Monarch Money Query Monarch Money data through a third-party MCP server.

Maintenance / activity evidence

GitHub REST pushed_at 2026-10-05T02:52:52Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Complete write authority is not verified.
Monarch Money credentials/session; independent integration
Sensitive access: Financial account and transaction data

Unofficial personal-finance integration; credentials and account data deserve high scrutiny; precise write surface not independently verified.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

411 repository stars

Stars observed Oct 9, 2026.

Repository total for robcerda/monarch-mcp-server.

All limitations / Review context

Has monarch-mcp-server changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

Unofficial personal-finance integration; credentials and account data deserve high scrutiny; precise write surface not independently verified.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Monarch Money credentials/session; independent integration
Financial account and transaction data
Sensitive access: Financial account and transaction data
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Monarch community integrations may use browser cookies or session tokens, and financial details are sensitive even in read-only mode.
Repository pushed_at explicitly observed

Original activity observations

GitHub REST pushed_at 2026-10-05T02:52:52Z

Technical identity

github.com/robcerda/monarch-mcp-server

Exact implementation source: https://github.com/robcerda/monarch-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: robcerda/monarch-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
robcerda/monarch-mcp-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Monarch Money MCP bridges personal financial data and MCP clients.
publisher setup entry · Publisher instructions
git clone https://github.com/robcerda/monarch-mcp-server.git cd monarch-mcp-server uv sync --locked
Configure / authenticate
MCP100 setup guide
Run uv run python login_setup.py in terminal for MFA/browser session before configuring the client. Use local stdio per README; do not place account passwords inside shared JSON.
Check connection
Suggested check
List tools or read an account list without editing transactions.
Remove / uninstall / revoke
MCP100 setup guide
Remove the `monarch` MCP entry from your selected client, for example Claude Code `claude mcp remove monarch` if that was your registration name. Stop the local Python server; uninstall its project virtualenv only if you no longer need it. Preserve financial data and unrelated credentials.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove monarch

Official Documentation & Sources

What it does

MCP Server for use with Monarch Money Query Monarch Money data through a third-party MCP server.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: Query Monarch Money data through a third-party MCP server

Representative uses

Summarize financial accounts
Find transactions and category expenses
Review budgets and account history
Query Monarch Money data through a third-party MCP server

Limitations

Unofficial personal-finance integration; credentials and account data deserve high scrutiny; precise write surface not independently verified.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Monarch community integrations may use browser cookies or session tokens, and financial details are sensitive even in read-only mode.
Repository pushed_at explicitly observed

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Monarch Money credentials/session; independent integration
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Financial account and transaction data
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: Unofficial personal-finance integration; credentials and account data deserve high scrutiny; precise write surface not independently verified.

Access scope and cautions

Write actions: Not verified
Sensitive access: Financial account and transaction data
Risk level: high
Security notes: Unofficial personal-finance integration; credentials and account data deserve high scrutiny; precise write surface not independently verified.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Summarize financial accounts; Find transactions and category expenses; Review budgets and account history; Query Monarch Money data through a third-party MCP server.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. Installation/authentication detail is incomplete; do not infer settings from package name. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Monarch Money credentials/session; independent integration

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Financial account and transaction data Recorded sensitive-access context: Financial account and transaction data.

What limitations and risks should I check before use?

Unofficial personal-finance integration; credentials and account data deserve high scrutiny; precise write surface not independently verified. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. Monarch community integrations may use browser cookies or session tokens, and financial details are sensitive even in read-only mode. Repository pushed_at explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.