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 分