Agents¶

Both supported clients use the same MCP command:

uvx slop-guard

That starts the local MCP server without any API calls or model-side judging. The tools return structured diagnostics that agents can use while they draft docs, release notes, or status updates.

The MCP surface is small on purpose. Agents can call check_slop when they already have text in memory, or check_slop_file when they need to inspect a file on disk. Both tools return structured JSON, so the client can point at exact spans and feed the advice back into the rewrite loop.

Codex¶

Register the server with Codex by pointing mcp add at uvx slop-guard, or add it to ~/.codex/config.toml:

[mcp_servers.slop-guard]
command = "uvx"
args = ["slop-guard"]

Claude Code¶

Register the server with Claude Code by pointing mcp add at uvx slop-guard, or add it to .mcp.json:

{
  "mcpServers": {
    "slop-guard": {
      "command": "uvx",
      "args": ["slop-guard"]
    }
  }
}

Pin a release¶

If an automation or team workflow needs a fixed package version, pin it in the command arguments:

uvx slop-guard==0.4.1

Use the release selector in this documentation site when you want the matching docs for that pinned version.

If you are deciding between a release and dev (main), use a release for stable automation and use dev (main) when you are testing current repository behavior before the next tag ships.