Lunch Money MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUNCHMONEY_API_TOKEN | Yes | Your Lunch Money API token |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_userA | Get details about the current Lunch Money user. Returns user information including:
Useful for verifying authentication and understanding the account context. |
| get_categoriesB | Return a list of category names. |
| get_transactionsA | Get transactions for a date range. This is a paginated tool and you MUST consider that not all transactions
may be returned. The include_aggregates returns aggregates for all pages. Args: start_date: Start date in YYYY-MM-DD format (required) end_date: End date in YYYY-MM-DD format (defaults to last day of start_date's month) filter_category_name: Filter by category name (e.g., "Groceries", "Dining Out") filter_tag_id: Filter by tag ID filter_status: Filter by transaction status (reviewed, unreviewed, delete_pending) filter_is_pending: Filter by pending status filter_manual_account_id: Filter by manual account ID filter_plaid_account_id: Filter by plaid account ID filter_recurring_id: Filter by recurring item ID include_pending: Include pending transactions (ignored if is_pending is set) limit: Maximum number of transactions to return (1-100, default 100) offset: Pagination offset include_aggregates: If True, calculates totals per category for full date range (respects all filters, except pagination) Returns: Structured JSON where transactions include category names instead of IDs, has_more pagination flag, and optionally category aggregates. When has_more is true, next_offset and next_limit are provided for easy pagination. |
| get_transactionA | Get details about a specific transaction. Retrieves the full details of a single transaction by its ID, including:
Args: transaction_id: ID of the transaction to retrieve Returns: Full transaction object with all available fields |
| add_numbersA | Helper tool for adding numbers together. LLMs should use this tool for arithmetic operations to avoid calculation errors. This is especially useful for summing expenses, calculating totals, or performing any arithmetic where precision matters. Args: numbers: List of numbers to add together. Can include negative values for subtraction. Returns: Dictionary with the sum rounded to 2 decimal places to avoid floating-point precision issues. |
| get_accountsA | Get all accounts (both manual and Plaid-synced). Returns a combined list of all accounts in the user's budget, including:
Each account includes minimal information: id, name, type, balance, currency, status, and account_type (to distinguish between 'manual' and 'plaid' accounts). Useful for understanding which accounts are available and their current balances. |
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 6 tools
Each tool targets a distinct resource or action: user info, categories, arithmetic, transaction list, single transaction, and accounts. No overlap or ambiguity.
All tools use a consistent verb_noun pattern in snake_case (e.g., get_current_user, get_transactions, add_numbers). No mixing of conventions.
6 tools is well-scoped for a personal finance MCP server covering user, categories, transactions, and accounts with a helper arithmetic tool. Not too many or too few.
The server is heavily read-only, missing write operations for transactions, categories, and accounts. The arithmetic helper is out of domain, and there are no create, update, or delete tools.