.mcp.json — Post-Publish Swap-In Notes for compliance-kb-mcp

The current .mcp.json at the repo root does not yet reference compliance-kb-mcp because it runs as a dev editable install via the API process. After the user publishes v0.2.0 to PyPI and npm, the following stanzas can be added to .mcp.json to reference the published package.

Option A — Python: uvx (zero global install, always latest patch)

{
  "mcpServers": {
    "compliance-kb": {
      "command": "uvx",
      "args": ["compliance-kb-mcp"]
    }
  }
}

Option B — Python: pip-installed CLI entrypoint

After pip install compliance-kb-mcp (or uv tool install compliance-kb-mcp):

{
  "mcpServers": {
    "compliance-kb": {
      "command": "compliance-kb-mcp"
    }
  }
}

Option C — Node: npx shim (delegates to Python)

The npm package @auditpilot/compliance-kb-mcp is a thin Node shim that spawns python -m compliance_kb_mcp.server. Python must be on PATH, or set the PYTHON environment variable to the desired interpreter path.

{
  "mcpServers": {
    "compliance-kb": {
      "command": "npx",
      "args": ["-y", "@auditpilot/compliance-kb-mcp"]
    }
  }
}

Current dev config (for reference)

The API process runs the server via:

python -m compliance_kb_mcp.server

using the editable install at packages/compliance-kb-mcp. Once the published version is available on PyPI, replace the editable install with uvx compliance-kb-mcp and update .mcp.json with Option A above.

Pinning to a specific version

To pin to v0.2.0 explicitly (recommended for production):

{
  "mcpServers": {
    "compliance-kb": {
      "command": "uvx",
      "args": ["compliance-kb-mcp==0.2.0"]
    }
  }
}