warmstart
An MCP server that exposes a verified manifest of a repository's development commands, allowing AI coding agents to instantly learn the correct dev loop without trial-and-error.
README
warmstart
Stop your AI agent from relearning your repo every session.
Every coding agent — Claude Code, Cursor, Codex, Copilot — pays the same tax on every repo, every session: it burns its first several turns guessing the test command, the build incantation, the package manager, the entry point, and stepping on gotchas the last session already figured out and threw away.
warmstart ends that. One command discovers your repo's real dev-loop, runs the commands to prove they work, and writes a committed AGENTS.md plus a live MCP server — so any agent reads the verified truth in one shot instead of fumbling.
npx warmstart init

Watch an agent waste 8 turns finding the test command → watch it read
AGENTS.mdand nail it in 1.
Why it's different from a hand-written AGENTS.md
A hand-written AGENTS.md rots the moment a command changes, so agents don't trust it and re-verify by trial anyway. warmstart keeps itself honest: every command carries a precise, scoped stamp of what was actually proven.
| Stamp | Meaning |
|---|---|
✓ passed — darwin/arm64, v20, 2026-06-22 |
Ran and exited 0 — here, then. Not a portability promise. |
~ flaky (2/3 passes) |
Non-deterministic across repeated runs. |
⚠ unverified (env-missing — command may be correct) |
Failed for a likely environmental reason (missing secret/service). |
⚠ unverified (not-run: destructive) |
Matched a dangerous pattern — never auto-run. |
⚠ unverified (timeout) / ✗ failed |
Recorded with a redacted, distilled reason. |
The stamp states what was proven, where, and when — never a bare "verified."
How it works
- Scan — mines your
package.jsonscripts,Makefiletargets, andpyproject.tomlfor candidate commands. - Consent — previews the exact command plan and asks before running anything.
- Verify — runs the safe candidates and records honest, scoped results.
- Emit — writes a delimited block in
AGENTS.md(never clobbering your prose) and registers awarmstart serveMCP server for Claude Code.
Plays nice with your existing AGENTS.md
Already have a hand-written AGENTS.md? warmstart never overwrites it and never errors — it appends a single delimited block and leaves everything else untouched. Your file ends up with two zones that coexist:
# My Project
Hand-written notes you care about. ← yours forever, never touched
## Gotchas
- Never run migrations on Friday.
<!-- warmstart:start -->
verified dev-loop commands ← warmstart owns / refreshes only this
<!-- warmstart:end -->
- First touch of a hand-written file → backs it up to
AGENTS.md.bak, then appends the block. - Re-runs are idempotent → warmstart replaces only the content between its markers (re-verifying the commands), so sections never stack up as duplicates.
- Your prose, architecture notes, and conventions stay yours. warmstart only manages the "how to actually run it" block.
Curated human knowledge above, machine-verified commands below — kept honest and current without stepping on your work.
Safety & privacy
- Runs fully locally. No telemetry. No network except your repo's own commands.
- Never auto-runs destructive commands.
deploy,publish,rm -rf,git push,drop, and similar are listed but never executed. - No shell execution. Commands run via
cross-spawnwith tokenized args — no shell-injection surface, and Windows.cmdshims work correctly. - Never commits secrets. Command output is redacted (tokens, credentials, home paths) and raw output is never embedded in
AGENTS.md. - Never clobbers your files. An existing hand-written
AGENTS.mdis backed up and preserved; only a delimited block is managed.
Configuration (.warmstartrc.json or .warmstartrc.yaml)
{
"timeoutMs": 120000,
"flakyRuns": 1,
"network": false,
"disable": ["make deploy"],
"env": {}
}
Commands
warmstart init— scan, verify (with consent), emitAGENTS.md+ register MCP.--yesfor non-interactive/CI.warmstart serve— run the MCP server exposing the manifest.warmstart doctor— check toolchain availability.
Supported sources
Now: package.json (+ pnpm/yarn/npm/bun detection), Makefile, pyproject.toml.
Planned: justfile, Taskfile.yml, tox.ini, CI workflows (as hint sources), passive observation, staleness re-verification, CI-stamped manifests.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。