Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Efficiency-governed MCP runtime, proxy, and benchmark CLI for LOVE (Lua) games.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"courtship": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/grimmdev/courtship:1.0.1"
]
}
}
}在终端中运行这条命令
claude mcp add courtship -- docker run -i --rm ghcr.io/grimmdev/courtship:1.0.1粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"courtship": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/grimmdev/courtship:1.0.1"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"courtship": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/grimmdev/courtship:1.0.1"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 grimmdev 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.0.1)于今天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Rystic
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The protocol layer between your agent and your LÖVE game.
courtship (court) is an all-in-one, efficiency-governed MCP runtime and task-level benchmarking harness for LÖVE game development. It natively encapsulates live-game inspection, code execution, Agent Joypad input simulation, safe crash recovery, and an offline LÖVE 12 API docs index in a single zero-dependency static binary, while also capable of acting as a governing efficiency proxy in front of existing upstream servers.
The LÖVE Model Context Protocol (MCP) ecosystem is functional but ungoverned. Raw bridges emit monolithic game state objects, eager documentation dumps, and hundreds of unpruned keys on every interaction, causing context bloat and runaway token cost.
Courtship acts as the measurement and remediation layer, proving three foundational claims:
| Claim | Goal | Empirically Measured | Status |
|---|---|---|---|
| 1. Standing Context Tax | Cut standing schema context by ≥70% | 76.5% reduction (340 vs 1,450 tokens) | Proven |
| 2. Response Shaping Spend | Cut per-task token spend by ≥40% | 53.4% average reduction | Proven |
| 3. Unified Router Efficiency | Beat separate MCP servers for mixed tasks | -40% latency, -33% calls via local FTS5 | Proven |
┌─────────────────┐ MCP (stdio/HTTP) ┌────────────────────────────────┐
│ AI Client │◄────────────────────────────►│ court proxy │ │ (Claude Code, │ ~340 token │ ├─ meta-tools (5 standing) │ │ Cursor, IDE) │ standing surface │ ├─ heuristic router │ └─────────────────┘ │ ├─ response shaper & cursors │ │ ├─ session token ledger │ │ └─ upstream pool manager │ └───────────────┬────────────────┘ │ MCP ┌──────────────────────────┼──────────────────────────┐ ▼ ▼ ▼ LovePilot LÖVE 12 Docs Custom Game Servers │ (SQLite FTS5) ▼ LÖVE Game (TCP 12345)
The proxy operates as a daemon with an internal registry, not a dumb passthrough. Tool schemas remain daemon-side until hydrated on-demand, expiring after N inactive turns.
Only 5 compact meta-tools are exposed permanently in standing context (~340 tokens), keeping context clean while allowing the agent to discover or invoke any game tool on-demand:
discover_tools(query, limit): Fuzzy discovery without schema ingestion.load_tool_schema(name): Hydrates full JSON schema on-demand.call_tool(name, args): Executes tool through compression filters.love_task(goal, context): Intelligent intent router (docs vs inspect vs exec).report_usage(): Session token, call, and latency accounting.call_tool & discover_tools)simulate_input(sequence): Agent Joypad: Dispatches timed keyboard inputs (press, keydown, keyup).step_frames(count, dt): Deterministic Frame Stepping: Advances physics by N ticks at fixed dt.get_last_crash(): Safe Crash Diagnostics: Non-fatal stack trace and locals recovery.clear_crash(): Resumes game loop after hot-patching.visual_diff(image_a, image_b): Visual Regression: Compares two screenshots and returns bounding boxes.get_objects(): Returns active entity coordinates and types in lean format.get_screenshot(): Returns downscaled, cropped PNG framebuffers.run_lua(code): Evaluates arbitrary Lua inside the game loop.love.errhand override)Prevents the infamous LÖVE "Blue Screen of Death" from crashing the process or severing the MCP bridge when an agent introduces a bug:
love.errhand to pause execution and render an in-game diagnostic HUD rather than terminating.debug.traceback(), and active local variables.get_last_crash(), write a fix, and hot-reload.Enables agents to test game mechanics that require time and movement:
D for 1.2s, press Space, release).love.update(dt) by exact frame counts at fixed delta time (default 1/60), eliminating wall-clock jitter when validating platformer physics and collisions.Every tool return and notification passes through deterministic shaping:
{id, type, name, x, y}." ".max_tokens.watch_game_state) suppress identical ticks to 0 tokens.court run)Wraps any existing LÖVE game dynamically:
court run ./mygame --mcp-port 12345
Automatically mounts source files and hooks love.update, love.draw, and the bridge without modifying your repository. For manual integration, court init generates the 5-line inline hook.
Running court bench --compare lovepilot,courtship on reference suites:
task tokens calls p95ms turns success
fix-double-jump 316 2 110 2 PASS spawn-coin 307 2 110 2 PASS
TOTAL (per task) 311 2 110 2 2/2 vs lovepilot -54.3% -33% -40% - -
court proxy --port 12345
court proxy --eager # Fallback exposing full upstream tools
# Compare candidate against raw baseline
court bench --suite ./suites/platformer.yaml --compare lovepilot,courtship
court bench --suite ./suites/platformer.yaml --ci --max-regression 10.0
court bench --suite ./suites/platformer.yaml --compare lovepilot,courtship --submit
court run ./fixtures/platformer
court run ./fixtures/platformer --shim-only
court docs search "rectangle"
court docs search "love.physics.newWorld"
court doctor
court doctor --ci
courtship.toml)[proxy]
port = 12345 max_response_tokens = 1500 evict_after_turns = 6 delta_notifications = true eager = false
[upstream.lovepilot] transport = "stdio" command = "uvx" args = ["--from", "./love-mcp", "love-mcp-server"] shape = { get_objects = "lean", get_screenshot = "scaled" }
[upstream.docs] transport = "builtin" index = "./lua54-love12.sqlite"
[bench] suite_dir = "./suites" baseline = ".courtship/baseline.json" max_regression = "10%"
Licensed under: