MCP server

The owlwarden MCP server

The MCP server exposes four read-only tools. It can scan files and explain rules, but it cannot write files or make network requests. Hooks handle enforcement.

Four read-only tools

  1. 01 scan_projectCheck the bounded workspace tree.
  2. 02 scan_fileInspect one path under the workspace root.
  3. 03 explain_ruleReturn the rule and its inline fix.
  4. 04 list_rulesExpose the compiled-in catalogue.
stdio, static analysis, workspace paths only
npx owlwarden mcp

When to use it

It is the right surface for the prompted, exploratory case: what does this rule mean, show me everything in packages/api.

MCP calls are optional because the model decides when to make them. Use hooks for checks that must run after edits or before commands.

Configuration

owlwarden init writes this for you: Claude Code, Cursor, or check a repository first.

{
  "mcpServers": {
    "owlwarden": {
      "command": "node_modules/.bin/owlwarden",
      "args": ["mcp"]
    }
  }
}

Invoked by path rather than npx -y owlwarden, because a server resolved at run time is a finding. The generated config uses the installed binary instead.

On a terminal

Run without a host and it prints a short how-to on stderr, then waits. Silence means it is waiting for a host, not that it hung.

Keep reading