Claude Desktop Setup

Configure Claude Desktop to use Comply as an MCP tool.

Prerequisites

• Claude Desktop installed
• Comply installed (see Installation)
• comply binary accessible in your PATH

Verify the binary path:

which comply

Note the output — you'll need it for the config.

Configuration

Open your Claude Desktop MCP configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the comply server to the mcpServers object:

{
  "mcpServers": {
    "comply": {
      "command": "/usr/local/bin/comply",
      "args": ["mcp"],
      "env": {
        "OPENROUTER_API_KEY": "sk-or-your-key-here"
      }
    }
  }
}

Replace /usr/local/bin/comply with the path from which comply.

Verify the connection

1. Restart Claude Desktop after saving the config
2. Start a new conversation
3. Ask Claude: "Use the comply_check tool to check my repo at /path/to/repo"

Claude will call comply_check with the path you specify and return structured results.

Example conversation

You: Check my diff at /Users/me/myproject for compliance issues.

Claude: I'll run a compliance check now.

(calls comply_check with repo_path=/Users/me/myproject)

Claude: The check found 1 issue: has-test-coverage failed — two new functions were added without corresponding tests. All other 8 rules passed.

Troubleshooting

"comply not found" — The command path is wrong. Run which comply and update the config.

"OPENROUTER_API_KEY not set" — Add the env block with your key as shown above.

Server doesn't appear in Claude — Ensure the JSON is valid (no trailing commas). Use a JSON validator if unsure.

Next steps

Configure Cursor to use the Comply MCP server.