Lunchmoney Mcp V2

What is Lunchmoney Mcp V2?

Lunchmoney Mcp V2 is the first MCP server built on the Lunch Money v2 API. It provides 14 tools for reading, creating, updating, deleting, and performing advanced operations on personal finance data (transactions, categories, tags, accounts, budgets, recurring items). Designed for users of Lunch Money who want to use AI assistants to manage their finances.

How to use Lunchmoney Mcp V2?

Add the server configuration to Claude Desktop or Claude Code’s MCP JSON file, setting the command to npx lunchmoney-mcp-v2 and the LUNCHMONEY_TOKEN environment variable to your API token (obtained from the Lunch Money Developer settings). Once connected, simply ask your LLM natural-language questions or commands.

Key features of Lunchmoney Mcp V2

• 14 tools covering read, CRUD, and advanced operations
• Hydrated responses: category, tag, and account names instead of raw IDs
• Smart caching: categories, tags, accounts cached at startup, auto-refreshed after mutations
• Type-safe: generated from the official OpenAPI spec via openapi-typescript

Use cases of Lunchmoney Mcp V2

• Reviewing and organizing unreviewed transactions by category or tag
• Getting a budget summary with income, spending, and per-category breakdown
• Adding, splitting, grouping, or deleting transactions via natural language
• Creating, updating, or deleting categories and tags to keep your organization tidy

FAQ from Lunchmoney Mcp V2

How do I get my Lunch Money API token?

Get your API token from the Lunch Money Developer settings page.

What tools does Lunchmoney Mcp V2 provide?

It offers 14 tools: get_user, list_transactions, list_categories, list_tags, get_accounts, get_summary, get_recurring, manage_transaction, manage_category, manage_tag, manage_account, bulk_update_transactions, split_transaction, and group_transactions.

What are the runtime or dependency requirements?

The server runs via npx (Node.js package runner). No additional local installation is needed beyond Node.js and npm. All data remains in the Lunch Money cloud; no local storage is used.

Are there any known limits or restrictions?

• Bulk updates are limited to 500 transactions at a time.
• Plaid‑synced accounts are read-only; only manual accounts can be created, updated, or deleted.

How is authentication and transport handled?

Authentication uses a Lunch Money API token passed via the LUNCHMONEY_TOKEN environment variable. The server communicates over MCP using standard stdio transport.