Lunch Money MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUNCH_MONEY_API_KEY | Yes | Your Lunch Money API key from https://my.lunchmoney.app/developers |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userA | Get information about the Lunch Money user connected to the configured API key. |
| get_categoriesA | List Lunch Money categories in flattened or nested form. |
| create_categoryC | Create a new Lunch Money category. |
| update_categoryC | Update an existing Lunch Money category. |
| get_tagsA | List all Lunch Money tags. |
| get_transactionsC | Get Lunch Money transactions with optional filters. |
| create_transactionC | Create one or more Lunch Money transactions. |
| update_transactionC | Update a Lunch Money transaction or split it into multiple child transactions. |
| get_assetsA | List manually managed Lunch Money assets. |
| create_assetC | Create a manually managed asset in Lunch Money. |
| get_plaid_accountsA | List Lunch Money Plaid-connected accounts. |
| trigger_plaid_fetchC | Trigger a Lunch Money fetch for eligible Plaid accounts. This queues a background fetch job. |
| get_budgetsA | Get Lunch Money budgets and spending for a date range. |
| upsert_budgetC | Create or update a Lunch Money budget entry for a category and month. |
| get_recurring_itemsA | Get Lunch Money recurring items for the current or specified month range. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct resource or action, with clear separation between asset, category, transaction, budget, account, recurring item, tag, and user operations. No overlapping functionality.
All tools follow a consistent verb_noun pattern (e.g., create_asset, get_transactions, update_category), using the same set of verbs (create, get, update, upsert, trigger) throughout.
With 15 tools, the server covers the core aspects of personal finance management without being overloaded or underdeveloped. Each tool has a clear purpose.
The server provides create, read, and update operations for several resources, but lacks delete operations for all resources and missing update for assets and recurring items. Tags only have a get operation, leaving significant gaps in the lifecycle.