Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Generate a recipe from ingredients on hand, with optional dietary restrictions. Free.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://chomptron.com/mcp在终端中运行这条命令
claude mcp add --transport http chomptron https://chomptron.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"chomptron": {
"url": "https://chomptron.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"chomptron": {
"type": "http",
"url": "https://chomptron.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://chomptron.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 swantron 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于上个月进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Microsoft Exchange Online MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Exchange Online admin for MSPs: forwarding audits, EWS posture and offboarding, no PowerShell
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
AI-powered recipe generator that transforms ingredients into delicious recipes using Google Gemini AI. Deployed on Google Cloud Run at chomptron.com.
Enter ingredients you have in your kitchen, and Chomptron generates creative, practical recipes complete with measurements, instructions, cooking time, and serving sizes.
npm install
export GEMINI_API_KEY="your-api-key-here" export GEMINI_MODEL="gemini-3.1-flash-lite" # Optional, defaults to gemini-3.1-flash-lite npm start
Visit http://localhost:8080
Get API key: https://makersuite.google.com/app/apikey
gemini-3.1-flash-liteThe Gemini model can be configured via the GEMINI_MODEL environment variable:
Recommended Models (as of December 2025):
limit: 0)December 2025 Quota Shift:
Google overhauled free tier quotas in December 2025:
gemini-2.0-flash was removed from fully unauthenticated free tierlimit: 0 errors for newer models without billing enabledFixing "Limit: 0" Errors:
If you're seeing quota errors with limit: 0:
/api/usage endpoint or https://ai.dev/usageFree Tier Limits (as of Dec 2025):
| Model | Requests/Minute | Requests/Day | Best For |
|---|---|---|---|
| gemini-2.5-flash-lite | 15 | 1,000 | High-volume apps |
| gemini-2.5-flash | 10 | 250 | General use |
| gemini-2.0-flash | 10 | 200 | Legacy (unstable) |
| gemini-2.5-pro | 2 | 50 | Complex reasoning |
npm test
Tests validate:
styles.css and app.js linking/health, /ready) and recipe generationjson { "ingredients": "chicken, tomatoes, garlic", "dietaryPreferences": { "vegan": false, "vegetarian": false, "glutenFree": false, "dairyFree": false, "nutFree": false, "shellfishFree": false, "eggFree": false, "soyFree": false } } json { "success": true, "recipe": "**Recipe Name:** ...", "cached": false } generate_recipe (ingredients + optional dietary flags). Unauthenticated. Daily cap MCP_DAILY_RECIPE_LIMIT (default 20), persisted to MCP_BUDGET_FILE so a process restart on the same instance does not reset it.Chomptron is built as a serverless application on Google Cloud Run for cost efficiency and automatic scaling.
Tech Stack:
Why Serverless?
Performance Optimizations:
Health checks:
curl https://chomptron.com/health
curl https://chomptron.com/ready curl https://chomptron.com/api/usage # View usage statistics
View logs:
# Recent logs
gcloud run logs read chomptron --region us-central1 --limit 50
gcloud run logs tail chomptron --region us-central1
Console dashboards:
Recipes are stored in browser localStorage with the following structure:
{
"id": "timestamp", "ingredients": "chicken, tomatoes, garlic", "recipe": "Full recipe text...", "recipeName": "Extracted recipe name", "timestamp": "2025-01-01T00:00:00.000Z", "favorite": false, "rating": 0, "notes": "", "servingSize": 4, "dietaryPreferences": { "vegan": false, "vegetarian": false, "glutenFree": false, "dairyFree": false, "nutFree": false, "shellfishFree": false, "eggFree": false, "soyFree": false } }
The application uses in-memory caching on the server side:
Optimized for search engines and social sharing with meta tags, Open Graph, Twitter Cards, structured data (JSON-LD), sitemap, robots.txt, and PWA support.
This repo includes a Buildkite pipeline at .buildkite/pipeline.yml that runs on a self-hosted GCP agent provisioned by buildkite-gcp-agent.
Push / PR
└── Three steps dispatched in parallel: ├── :prettier: Format check (npm run format -- --check) ├── :eslint: Lint (npm run lint) └── :nodejs: Tests (npm test) └── Annotate — consolidated pass/fail surfaced in the Buildkite UI
The key difference from the GitHub Actions workflow, which runs format → lint → test sequentially in a single job: these three steps have no dependencies on each other and run simultaneously. On a pool of agents this distributes the work; even on a single agent the explicit dependency graph documents intent and makes the pipeline trivially scalable.
The deploy stage is intentionally omitted — Cloud Run deployments are handled by the existing GHA workflow which holds the production GCP credentials. CI (fast feedback) and CD (production access) are kept in separate systems as a security boundary.
Connect the repo via Buildkite → New Pipeline → point at github.com/swantron/chomptron. Buildkite reads .buildkite/pipeline.yml automatically on each push.
All steps run on the gcp queue:
agents:
queue: gcp
This is a personal project, but suggestions and improvements are welcome!
MIT