Monarch Money TypeScript SDK

Created By
martinampsa year ago
small mcp server for accessing monarch money
Overview

what is Monarch Money TypeScript SDK?

Monarch Money TypeScript SDK is a library designed for accessing financial data from Monarch Money, enabling developers to integrate financial management features into their applications.

how to use Monarch Money TypeScript SDK?

To use the SDK, install it via npm or bun, and authenticate using a browser token or standard login credentials to access various financial data methods.

key features of Monarch Money TypeScript SDK?

  • Access to user accounts, transactions, and budgets.
  • Support for both token-based and standard authentication.
  • MCP server for AI agents to interact with financial data.

use cases of Monarch Money TypeScript SDK?

  1. Integrating personal finance management into web applications.
  2. Building financial analytics tools that require access to user transaction data.
  3. Developing AI agents that can query financial information through the MCP server.

FAQ from Monarch Money TypeScript SDK?

  • Is the SDK free to use?

Yes! The Monarch Money TypeScript SDK is free to use for developers.

  • What programming language is the SDK written in?

The SDK is written in TypeScript, making it suitable for modern web applications.

  • Can I use the SDK without a Monarch Money account?

No, you need a Monarch Money account to access the data through the SDK.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
martinamps
Star
1
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago