Skip to main content

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.

{
    "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.

Client Install
Claude Code claude plugin marketplace add juftin/lunchmoney-app && claude plugin install lunchmoney-mcp@lunchmoney-app
Codex codex plugin marketplace add juftin/lunchmoney-app && codex plugin add lunchmoney-mcp@lunchmoney-app
Gemini CLI gemini extensions install https://github.com/juftin/lunchmoney-app
Claude Desktop Download 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.

Metadata

Release files for lunchmoney-app 0.15.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lunchmoney-app 0.15.2
File Size Uploaded
lunchmoney_app-0.15.2.tar.gz 713.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for lunchmoney-app 0.15.2
File Interpreter ABI Platform
lunchmoney_app-0.15.2-py3-none-any.whl Python 3 none any Details

Total release size: 988.9 kB

Release files / lunchmoney_app-0.15.2.tar.gz

Download URL lunchmoney_app-0.15.2.tar.gz
Size 713.9 kB
Tags Source
SHA-256 checksum
How to use checksums
69dc9d2eacb152eba1738ecf5113fa710d82dc296a3a300b5088b2f77df537a5
BLAKE2b-256 checksum
How to use checksums
3be57cde3b51e5d5c4fe56ea786e8b26c37d9cdd6033b3ab5717f97cab48ebc0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.

Transparency log

Release files / lunchmoney_app-0.15.2-py3-none-any.whl

Download URL lunchmoney_app-0.15.2-py3-none-any.whl
Size 275.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
907c2f14afc26170947c50979336da4ea8336bf2e465d4127375bdcee78e1c35
BLAKE2b-256 checksum
How to use checksums
d27042dc82aa707b6f04e7231d9342edadd7f0a0b79bc034f5afa8392d30f3ad
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.15.2 This release

2 release files

0.15.1

2 release files

0.15.0

2 release files

0.13.0

2 release files

0.12.0

2 release files

0.11.1

2 release files

0.11.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page