DOS — Claude Code MCP server: what it does and setup
DOS checks agent claims against Git artifacts, spots file collisions, and flags stalled runs. Use it when several agents work in one repository.
claude mcp add --env DISPATCH_WORKSPACE=<DISPATCH_WORKSPACE> --transport stdio dos-the-trust-substrate-for-agent-fleets -- uvx dos-kernelWhat DOS — the trust substrate for agent fleets does
DOS tests an agent’s report against the work left behind in Git. dos verify returns SHIPPED with exit code 0 when a commit supports the claim, or NOT_SHIPPED with exit code 1 when nothing landed. It can also surface agents touching the same files and runs that stop making progress.
The MCP server starts with uvx dos-kernel. Its workspace can be supplied through DISPATCH_WORKSPACE, with ready-made setup commands for Claude Code, Codex, Cursor, GitHub Copilot, and Gemini CLI. For direct repository setup, the project instructions use dos-kernel, dos init --hooks auto, and dos doctor.
DOS works against a Git repository and uses PyYAML as its runtime dependency. Set DISPATCH_WORKSPACE to the intended directory in the MCP configuration; otherwise the checks point at the wrong workspace.
What it helps with
- verify that a claimed change reached Git
- separate backed commits from false completion reports
- spot agents writing over the same files
- flag a run that keeps spinning without progress
Example prompts for the agent
- Check whether claim
AUTH1actually shipped and report the result withdos verify. - Compare the agents’ claims with the repository commits and find claims that did not land.
- Inspect this workspace for file collisions between active agents.
How to install DOS — the trust substrate for agent fleets
Platform CLI
claude mcp add --env DISPATCH_WORKSPACE=<DISPATCH_WORKSPACE> --transport stdio dos-the-trust-substrate-for-agent-fleets -- uvx dos-kernelReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>
Platform CLI
codex mcp add dos-the-trust-substrate-for-agent-fleets --env DISPATCH_WORKSPACE=<DISPATCH_WORKSPACE> -- uvx dos-kernelReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>
Config file
{
"mcpServers": {
"dos-the-trust-substrate-for-agent-fleets": {
"command": "uvx",
"args": [
"dos-kernel"
],
"env": {
"DISPATCH_WORKSPACE": "<DISPATCH_WORKSPACE>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>
Config file
{
"servers": {
"dos-the-trust-substrate-for-agent-fleets": {
"type": "stdio",
"command": "uvx",
"args": [
"dos-kernel"
],
"env": {
"DISPATCH_WORKSPACE": "<DISPATCH_WORKSPACE>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>
Platform CLI
gemini mcp add -e DISPATCH_WORKSPACE=<DISPATCH_WORKSPACE> dos-the-trust-substrate-for-agent-fleets uvx dos-kernelReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from dos-kernel <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about DOS — the trust substrate for agent fleets
How do I install DOS in Claude Code?
Run claude mcp add dos-kernel -- uvx dos-kernel.
What does DOS do?
DOS compares agent claims with Git artifacts. It reports SHIPPED or NOT_SHIPPED, and can identify file collisions and stalled runs.
Which platforms can use DOS as an MCP server?
It supports Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, and Gemini CLI.
