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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.