warmstart
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@warmstartinit dev commands for this project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 initWatch 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 |
| Ran and exited 0 — here, then. Not a portability promise. |
| Non-deterministic across repeated runs. |
| Failed for a likely environmental reason (missing secret/service). |
| Matched a dangerous pattern — never auto-run. |
| Recorded with a redacted, distilled reason. |
The stamp states what was proven, where, and when — never a bare "verified."
Related MCP server: instagit
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.
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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dadwritestech/warmstart'
If you have feedback or need assistance with the MCP directory API, please join our Discord server