lunchmoney-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUNCHMONEY_TOKEN | Yes | Your Lunchmoney API token, which you can get from your Lunchmoney developer settings (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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-budget-summaryC | Get budget summary for a specific time period |
| get-recent-transactionsC | Get recent transactions |
| search-transactionsC | Search transactions by keyword |
| get-category-spendingC | Get spending in a category |
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 4 tools
Each tool has a clearly distinct purpose: get-budget-summary targets budget overviews, get-category-spending focuses on category-level data, get-recent-transactions retrieves chronological transaction lists, and search-transactions enables keyword-based queries. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb-noun pattern with hyphens (e.g., get-budget-summary, search-transactions). The naming is uniform across all four tools, using 'get' for retrieval operations and 'search' for querying, which enhances predictability and readability.
With 4 tools, the count is reasonable for a personal finance domain, covering key operations like summaries, category analysis, and transaction retrieval. However, it feels slightly thin as it lacks tools for creating or updating data (e.g., adding transactions or categories), which might be expected in a full-featured finance server.
The tool set covers read-only operations well, including summaries, category spending, and transaction searches, but there are notable gaps. It lacks CRUD capabilities for transactions, categories, or budgets (e.g., create, update, delete), which limits agents to viewing data without modifying it, potentially causing workflow dead ends.