rocketmoney-mcp

A read-only Model Context Protocol server for Rocket Money. It lets an MCP client (Claude Desktop, claude.ai, etc.) browse your accounts, transactions, spending, budgets, net worth, and subscriptions so you can talk to an assistant about your finances.

It performs no write operations — every tool is annotated readOnlyHint and the server never mutates anything in your Rocket Money account.

Tools

All amounts are returned in USD.

Related MCP server: Monarch Money MCP Server

How auth works

Rocket Money has no third-party OAuth, so this server reuses your own web session. You grab the tb.auth0.sid cookie from a logged-in app.rocketmoney.com browser tab and paste it into the server's /auth page. The server keeps a rotating cookie jar (Rocket Money re-issues the cookie on every response, ~3h48m rolling TTL) persisted to disk, and runs a keepalive loop. There is no offline refresh token, so when the session eventually expires you re-paste a fresh cookie.

The cookie lives only on the machine running this server and is sent only to Rocket Money's own API.

Endpoints

Running locally

npm install
npm run build
ROCKETMONEY_STATE_DIR=./.state PORT=8080 node dist/index.js
# open http://localhost:8080/auth and paste your cookie

Environment

Deployment

Designed to run behind an authenticating gateway (e.g. a Cloudflare Access / OAuth front door) so the /mcp and /auth endpoints are never exposed unauthenticated — the server itself holds a live financial session and must not be publicly reachable.

Notes

• If a tool returns PersistedQueryNotFound, Rocket Money rotated a GraphQL query hash; re-capture it from a fresh HAR and update PERSISTED in src/rm/client.ts.

• Not affiliated with or endorsed by Rocket Money / Rocket Companies.

License

MIT