Lunch Money MCP (Unofficial)

io.github.n3wth由 GitHub 账号 n3wth 发布v0.1.0更新于 Oct 27, 2026

Read-only Lunch Money accounts, transactions, categories and budgets. Unofficial connector.

已验证Streamable HTTP可网页运行效率与工作流金融

概览

AI 生成的概览

非官方托管的 MCP 连接器,让 AI 助手以只读方式查看你的 Lunch Money 账户、交易、分类、预算和周期性支出。

可以做什么
  • 读取账户与余额,并按币种分别呈现
  • 查询交易记录,可按日期范围筛选或按分类汇总
  • 查看分类,并将本月支出与预算对比
  • 列出周期性支出
  • 在助手内连接、替换或移除 Lunch Money 连接
适用场景
适合想用对话方式了解自己 Lunch Money 账务的场景,例如按分类查看上周支出、对比预算执行情况或梳理周期性扣款,无需手动导出数据。
运行要求
需要 Lunch Money 账户,以及在 Lunch Money 开发者页面创建的个人访问令牌。需要支持远程服务器与 OAuth 登录的 MCP 客户端;先在连接器的认证站点登录,再在第三方连接服务的浏览器页面填入令牌。托管端点目前处于测试阶段。
安装前请注意
连接器会把你的 Lunch Money 令牌交由第三方连接服务保存,并在需要时取用;该令牌在 Lunch Money 中可能拥有比服务器所限制的只读范围更大的权限。登录、连接记录与请求会经过多个外部服务,结果还会进入你的 AI 客户端,并可能传给其模型提供商。连接类工具可替换或移除连接,而卸载客户端插件并不会撤销授权;如需彻底停用,请在 Lunch Money 中吊销该令牌。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Lunch Money MCP (Unofficial),将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.n3wth%2Flunchmoney-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "lunch-money-unofficial": {
      "type": "http",
      "url": "https://mcp.lunchmoney.sh/mcp"
    }
  }
}

README

Lunch Money for Agents

[Lunch Money for Agents icon]

Ask your AI agent about your Lunch Money data.

Website · Setup guide · Privacy · Report an issue

I built this to make Lunch Money easier to use with AI agents. It connects your account to tools that support Model Context Protocol (MCP), so you can ask about your spending, budgets, accounts, and recurring expenses in conversation.

This is an unofficial, open-source MCP integration by n3wth. It is not affiliated with, endorsed by, or sponsored by Lunch Money.

What you can ask

  • “Show my transactions from last week, grouped by category.”
  • “How does this month's spending compare with my budget?”
  • “List my recurring expenses.”
  • “What are my account balances? Keep each currency separate.”

The integration gives your agent access to the underlying records; your agent uses those results to answer. Financial access is read-only: it cannot edit transactions, change budgets, or move money. Connection tools can link, replace, or remove your connection to the service.

Connect your account

You'll need a Lunch Money account, a personal access token, and an MCP client that supports remote servers with OAuth sign-in.

  1. Add the server using your client's setup instructions below.
  2. Sign in at auth.n3wth.com. This creates your connector session, separate from your Lunch Money login.
  3. Ask your agent to connect Lunch Money. It should run lunchmoney_connect and give you a browser link.
  4. Open the link and enter your token in Nango's connection page. Create the token on Lunch Money’s Developers page by clicking Request New Access Token (label and usage are optional). Never paste it into chat or your MCP configuration.
  5. Try a small request, such as “List my Lunch Money accounts.”

The hosted endpoint is:

text
https://mcp.lunchmoney.sh/mcp

Client-specific installation

Choose your app on the website, or install directly:

Claude Code — run inside Claude Code:

text
/plugin marketplace add n3wth/lunchmoney-mcp/plugin install lunchmoney@lunchmoney-mcp

Codex — run in a terminal:

sh
codex plugin marketplace add n3wth/lunchmoney-mcpcodex plugin add codex-plugin@lunchmoney-mcp

For the Codex app, use Plugins → Create menu → Add marketplace with n3wth/lunchmoney-mcp, then install Lunch Money. Cursor — Add to Cursor, the Cursor directory listing, or select Cursor on the website. Start a new session after installing, sign in, then ask “Connect Lunch Money”.

Custom marketplaces are separate from curated directory approvals. Full instructions and manual alternatives:

ClientInstructions
CodexPlugin and manual setup
Claude CodePlugin setup
CursorPlugin and MCP configuration
Other MCP clientsConnection guide

The hosted service is in beta. Direct setup is available; a directory submission does not mean a plugin is approved or listed. See the submission record for review status and the runbook for outstanding release checks.

Where your data goes

Signing in and connecting Lunch Money are separate steps:

ServiceRole
Auth0Signs you in at auth.n3wth.com and identifies your connector account.
NangoCollects and stores your Lunch Money token through its browser flow.
CloudflareRuns the MCP server and stores identity and connection records.
Lunch MoneyReturns the financial records requested through its API.
Your AI clientReceives the results and may send them to its model provider.
VercelHosts the website and routes requests to the MCP server.

The server retrieves your token from Nango when needed and enforces financial reads only. Your token may have broader permissions in Lunch Money itself. Financial responses are not saved in the connector's database, but your AI client's privacy and retention settings still apply to the results it receives.

To disconnect, ask your agent to run lunchmoney_disconnect. If deletion fails, retry until it succeeds. Revoke the original token in Lunch Money if you also want to prevent its use elsewhere. Removing a client plugin does neither.

Read the privacy notice for storage, retention, and provider details, and the service terms before connecting your account.

A couple of things to watch

Transactions arrive in pages. One response may not cover the whole date range. The agent needs to follow next_offset until it is null before presenting a complete total.

Currencies stay separate. Adding USD and CAD amounts together does not produce a useful total. Ask for separate totals unless you explicitly want a conversion.

AI-generated answers can be wrong. Check the source records in Lunch Money when an answer matters. The user guide lists the tools and explains connection troubleshooting.

Work on the project

Use Node.js 22 or later. The site is static HTML and CSS with a small React conversation preview built from Vercel AI Elements.

bash
git clone https://github.com/n3wth/lunchmoney-mcp.gitcd lunchmoney-mcpnpm cinpm run preview

This serves the site at http://localhost:4173. To build it without starting a server, run npm run build; the output goes into dist/.

Run the server checks in dependency order:

bash
npm --prefix packages/auth-contract cinpm --prefix packages/auth-contract testnpm --prefix packages/lunchmoney-adapter cinpm --prefix packages/lunchmoney-adapter testnpm --prefix packages/server cinpm --prefix packages/server testnode scripts/validate-release.mjs
DirectoryContents
site/Website, styles, and shared icons
packages/MCP server, authentication contract, API adapter, and client plugins
docs/Setup, operations, security, and submission records
scripts/Release validation and smoke checks

Staging and production use separate configurations and databases. Default Worker commands target staging. Follow the runbook for deployment, credentials, migrations, and rollback.

Context7 documentation indexing

context7.json configures which documentation Context7 indexes. It includes this README, the documentation overview, connection, tools, and privacy guides, and the Codex, Claude Code, and Cursor setup guides. Internal plans, operational records, and agent instructions are excluded. Context7 always includes root Markdown files unless excluded by name.

After merging this file into the repository's default branch, open the Context7 library settings, switch the configuration source to the repository's context7.json if it is currently managed in the dashboard, and refresh the library. Verify the indexed sources include the setup guides and omit the excluded records.

See Context7's configuration reference for supported fields. This controls indexing only; a hosted Docs7 site uses a separate docs.json configuration.

Contribute

Bug reports, clearer setup instructions, and compatibility fixes are welcome. For a bug, include the client you used, what you expected, and a minimal example with sample data. Leave tokens and personal financial records out of issues.

Open an issue before a larger change so we can agree on the scope. For a pull request, explain the problem and how you checked the fix. Keeping financial access read-only is a core constraint of this project.

来源:README.md,提交 1676593

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v0.1.0最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分