Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Read-only Lunch Money accounts, transactions, categories and budgets. Unofficial connector.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://mcp.lunchmoney.sh/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http lunchmoney https://mcp.lunchmoney.sh/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"lunchmoney": {
"url": "https://mcp.lunchmoney.sh/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"lunchmoney": {
"type": "http",
"url": "https://mcp.lunchmoney.sh/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://mcp.lunchmoney.sh/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
서버가 도구 목록을 보여 주기 전에 로그인을 요구해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 10일 점검
레지스트리 이름이 GitHub 계정 n3wth 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
365ms 만에 응답(HTTP 401)
OAuth 로그인을 지원한다고 밝혀서, AI 앱이 로그인 화면으로 안내해 줘요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.0)은 2개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, ActivitySmith
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
AI agents and scripts reporting back to your iPhone with Push Notifications and Live Activities.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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.
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.
You'll need a Lunch Money account, a personal access token, and an MCP client that supports remote servers with OAuth sign-in.
lunchmoney_connect and give you a browser link.The hosted endpoint is:
https://mcp.lunchmoney.sh/mcp
Choose your app on the website, or install directly:
Claude Code — run inside Claude Code:
/plugin marketplace add n3wth/lunchmoney-mcp
/plugin install lunchmoney@lunchmoney-mcp
Codex — run in a terminal:
codex plugin marketplace add n3wth/lunchmoney-mcp
codex 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:
| Client | Instructions |
|---|---|
| Codex | Plugin and manual setup |
| Claude Code | Plugin setup |
| Cursor | Plugin and MCP configuration |
| Other MCP clients | Connection 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.
Signing in and connecting Lunch Money are separate steps:
| Service | Role |
|---|---|
| Auth0 | Signs you in at auth.n3wth.com and identifies your connector account. |
| Nango | Collects and stores your Lunch Money token through its browser flow. |
| Cloudflare | Runs the MCP server and stores identity and connection records. |
| Lunch Money | Returns the financial records requested through its API. |
| Your AI client | Receives the results and may send them to its model provider. |
| Vercel | Hosts 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.
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.
Use Node.js 22 or later. The site is static HTML and CSS with a small React conversation preview built from Vercel AI Elements.
git clone https://github.com/n3wth/lunchmoney-mcp.git
cd lunchmoney-mcp npm ci npm 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:
npm --prefix packages/auth-contract ci
npm --prefix packages/auth-contract test npm --prefix packages/lunchmoney-adapter ci npm --prefix packages/lunchmoney-adapter test npm --prefix packages/server ci npm --prefix packages/server test node scripts/validate-release.mjs
| Directory | Contents |
|---|---|
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.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.
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.