Lunch Money MCP

io.github.juftinPublished by GitHub account juftinv0.15.2Updated Oct 25, 2026

MCP-first access to your Lunch Money data.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

A local MCP server that gives an assistant access to your Lunch Money personal finance data, such as spending and transactions.

What you can do
Query spending totals for a period, such as dining this month, from your synced Lunch Money data. List and review recent transactions, including the largest ones. Find transactions that still need a category. Runs alongside a standalone app with a REST API and database that keeps itself in sync with your Lunch Money data.
When to use it
Use it when you want to ask an assistant questions about your own Lunch Money budgeting and transaction data in natural language, for example monthly spending or uncategorized transactions.
Requirements
Runs as a local process started by your MCP client; do not run a separate server command. Needs a Lunch Money access token supplied through the LUNCHMONEY_ACCESS_TOKEN environment variable. Claude Code, Codex and Gemini CLI installs use uvx, so uv must be installed; Claude Desktop uses the MCPB package.
Before you install
It requires your Lunch Money access token, a credential granting access to your financial account data; keep it private. The server syncs your Lunch Money data into a local database, so financial data is stored on your machine. Review what the assistant can read before connecting it.

Installation

In SourceWeft

  1. Open Lunch Money MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

lunchmoney-app

MCP-first access to your Lunch Money data

[GitHub] [GitHub License] [CI Status] [docs]

lunchmoney-app is first and foremost an MCP server for using your Lunch Money data from an MCP-enabled assistant. It also runs as a standalone application with a RESTful API and database backend that keeps itself in sync with all of your Lunch Money data.

Quickstart

Use Lunch Money from your favorite MCP-enabled assistant in a few minutes.

  1. Create or copy your Lunch Money access token.
  2. Add the configuration below to your MCP client's server settings.
  3. Replace your-lunch-money-token, restart the client, and start chatting.

Your MCP client starts and manages Lunch Money MCP for you; do not run a separate server command.

json
{    "mcpServers": {        "lunchmoney": {            "command": "uvx",            "args": ["lunchmoney-app", "mcp"],            "env": {                "LUNCHMONEY_ACCESS_TOKEN": "your-lunch-money-token"            }        }    }}

Try asking:

  • “How much did I spend on dining this month?”
  • “Show my largest recent transactions.”
  • “Which transactions still need a category?”
Install in Claude Code, Codex, Gemini CLI, or Claude Desktop

Claude Code, Codex, and Gemini CLI use the published package through uvx; install uv first. Claude Desktop manages the MCPB runtime itself. Provide your Lunch Money access token through LUNCHMONEY_ACCESS_TOKEN unless the client prompts for it.

ClientInstall
Claude Codeclaude plugin marketplace add juftin/lunchmoney-app && claude plugin install lunchmoney-mcp@lunchmoney-app
Codexcodex plugin marketplace add juftin/lunchmoney-app && codex plugin add lunchmoney-mcp@lunchmoney-app
Gemini CLIgemini extensions install https://github.com/juftin/lunchmoney-app
Claude DesktopDownload lunchmoney-app.mcpb from a release and open it.

For direct standard-MCP setup and framework-specific token configuration, see the MCP guide.

Learn more

  • MCP guide: client configuration, remote connections, and OAuth.
  • CLI guide: commands, data handling, scheduling, and shell completion.
  • Operations runbook: self-hosting, Docker Compose, security, and backups.

Source: README.md at commit 9b8218e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.15.2LatestOct 17, 2026
  2. v0.15.0Oct 15, 2026
  3. v0.14.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts