Blu3Ph4ntom/warden-mcp
Platform-specific configuration:
{
"mcpServers": {
"warden-mcp": {
"command": "npx",
"args": [
"-y",
"warden-mcp"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
Warden MCP is a plan-governance MCP server for coding agents. It keeps agents on a concrete execution plan, makes progress explicit, and blocks premature "done" claims with finish-gate checks.
If you just want the easiest local install for an MCP-capable coding agent, use npm:
npm install -g warden-mcp
warden-mcp healthThen add this MCP server entry:
{
"mcpServers": {
"warden": {
"command": "warden-mcp",
"args": []
}
}
}After your client connects, call these tools in order:
get_agent_guidehealth_checkget_statusIf your client supports Claude Code-style local MCP config, the same warden-mcp entry should work there too. That includes Claude Code directly and Claude-compatible setups such as Auggie-style local MCP flows.
If you prefer Claude Code's plugin flow, this repository ships a repo-root plugin and marketplace entry.
/plugin marketplace add https://github.com/Blu3Ph4ntom/warden-mcp/plugin, install warden-mcp, and enable it for your project or sessionThe plugin launches Warden with npx -y warden-mcp, so Claude Code downloads the published npm package on first run instead of requiring a separate global install.
This plugin now ships three layers for Claude Code and compatible clients:
.mcp.json)hooks/hooks.json) for enforced completion gatingcommands/warden-start.md, commands/warden-next.md, commands/warden-finish.md)The hooks are the important part: on Stop, the client calls Warden's finish gate and gets blocked from stopping when required work remains.
The shared marketplace hook config intentionally uses a conservative event subset that loads in Augment-compatible clients too. Richer Claude lifecycle events such as `TaskC
Loading reviews...