Skip to main content
Glama
leafeye

lunchmoney-mcp-v2

by leafeye

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LUNCHMONEY_TOKENYesYour 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_userA

Get the current Lunch Money user's account info: name, email, budget name, and primary currency.

list_transactionsA

List or look up Lunch Money transactions. Without an id, returns filtered transactions (defaults to last 30 days if no dates given). With an id, returns that single transaction.

Filters: start_date/end_date (YYYY-MM-DD), category_id, tag_id, status (reviewed/unreviewed), account_id. Use limit/offset for pagination.

Returns hydrated output with category names, tag names, and account names instead of raw IDs.

manage_transactionA

Create, update, or delete a single Lunch Money transaction.

action="create": Provide date (YYYY-MM-DD), amount (positive=debit, negative=credit), and optionally payee, category_id, notes, account_id, tag_ids, currency. action="update": Provide id and any fields to change (payee, amount, date, category_id, notes, tag_ids, status). action="delete": Provide only the id of the transaction to delete.

bulk_update_transactionsA

Update multiple transactions at once (max 500). Each item needs an id plus the fields to change.

Common uses: batch-categorize transactions, bulk mark as reviewed, assign tags to multiple transactions. Fields per transaction: category_id, payee, notes, tag_ids, status, date, amount, currency.

split_transactionA

Split or unsplit a Lunch Money transaction.

action="split": Provide id of the transaction to split, plus a splits array. Each split has amount (required) and optionally payee, date, category_id, notes. The split amounts MUST add up to the parent transaction amount. action="unsplit": Provide id of the split parent to restore it to normal.

group_transactionsA

Group or ungroup Lunch Money transactions.

action="group": Combine multiple transactions into one grouped transaction. Provide ids (array of transaction IDs), date (YYYY-MM-DD), and payee (required). Optionally set category_id, notes, tag_ids. The grouped transaction amount equals the sum of the original amounts. action="ungroup": Provide id of the group parent to restore original transactions.

list_categoriesA

List all Lunch Money categories. Use format="nested" to see category groups with their children, or format="flat" (default) for a flat list.

manage_categoryA

Create, update, or delete a Lunch Money category.

action="create": Provide name (required). Optionally set description, is_income, exclude_from_budget, exclude_from_totals, is_group, group_id. action="update": Provide id and any fields to change (name, description, is_income, exclude_from_budget, exclude_from_totals, archived, group_id). action="delete": Provide id. Use force=true to delete even if the category has dependent transactions/rules.

list_tagsA

List all Lunch Money tags. Tags can be assigned to transactions for additional organization beyond categories.

manage_tagA

Create, update, or delete a Lunch Money tag.

action="create": Provide name (required). Optionally set description. action="update": Provide id and any fields to change (name, description, archived). action="delete": Provide id. Use force=true to delete even if the tag is used on transactions.

get_accountsA

Get all Lunch Money accounts — both manual accounts and synced (Plaid) accounts. Shows balances, types, and status.

manage_accountA

Create, update, or delete a manual Lunch Money account. Synced (Plaid) accounts are read-only.

action="create": Provide name, type (cash/credit/cryptocurrency/employee compensation/investment/loan/other liability/other asset/real estate/vehicle), and balance (required). Optionally set institution_name, currency, subtype. action="update": Provide id and any fields to change (name, balance, institution_name, display_name, status, subtype). action="delete": Provide id. WARNING: this permanently deletes the account. Transactions are NOT deleted by default.

get_summaryA

Get a budget summary for a date range. Shows income, spending, and per-category breakdown with budget vs actual. If the date range aligns with budget periods, budget amounts and availability are included.

Tip: Use the first and last day of a month for a monthly overview (e.g. 2026-02-01 to 2026-02-28).

get_recurringA

Get recurring items (subscriptions, bills, income). Shows expected amounts, frequency, and match status for the given period. Without dates, uses the current month.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a distinct resource or operation. Read (list/get), write (manage), batch (bulk_update), and structural operations (split/group) are clearly separated, minimizing the chance of misselection.

Naming Consistency4/5

The naming follows a verb_noun convention with intuitive prefixes like get_/list_, manage_, bulk_update_, split_, and group_. The only minor inconsistency is mixing get_ and list_ for read operations (e.g., get_accounts vs list_transactions), but the pattern is still predictable.

Tool Count5/5

With 14 tools, the server covers user info, transactions, categories, tags, accounts, recurring items, and budget summaries—each earning its place. This is within the ideal 3-15 range and feels well-scoped.

Completeness4/5

The tool set provides solid coverage for core CRUD on transactions, categories, tags, and accounts, plus advanced transaction operations (split/group/bulk update). Minor gaps exist, such as recurring items being read-only and no bulk delete, but agents can work around these.

Maintenance

ActivityInactive
ResponsivenessNo issues