ControlKeel
Run governed MCP workflows with policy checks, tracked findings, and explicit review gates before agents ship changes.
Overview
ControlKeel is a MCP server for the Ship phase that enforces governed workflows with policy validation, findings, and review gates.
What is this MCP server?
- Policy validation on MCP-driven workflows
- Findings tracking for issues the agent or tools surface
- Review gates before risky operations complete
- npm package @aryaminus/controlkeel with npx stdio transport
- Registry version 0.2.29 on GitHub aryaminus/controlkeel
- npm identifier @aryaminus/controlkeel
- stdio transport via npx runtimeHint
What problem does it solve?
Unrestricted MCP tool chains let agents merge risky changes with no audit trail or approval step.
Who is it for?
Solo builders who rely heavily on MCP automation and want lightweight governance without building a custom CI policy engine.
Skip if: One-shot scripts or teams with zero appetite for configuring policies and gates.
What do I get? / Deliverables
Workflows run under policies, record findings, and pause at review gates until you explicitly allow progression.
- Policy-validated MCP workflow execution
- Recorded findings for agent-driven actions
- Review gate checkpoints before completion
Recommended MCP Servers
Journey fit
How it compares
MCP workflow governor with audit flavor, not a vulnerability scanner or lint skill.
Common Questions / FAQ
Who is ControlKeel for?
Indie developers and small teams using MCP agents who need policy checks and review gates on automated workflows.
When should I use ControlKeel?
Before scaling agent-driven refactors, deployments, or multi-tool pipelines where mistakes are costly.
How do I add ControlKeel to my agent?
Add the npm MCP server @aryaminus/controlkeel with runtimeHint npx and stdio transport in your client MCP settings.