Corveil MCP client setup

Corveil exposes all of its first-party tools from one MCP endpoint, /mcp, over Streamable HTTP. Point your client there and authenticate with a virtual API key (or browser OAuth — see the reference).

Claude Code (~/.config/claude-code/mcp.json)

{
  "mcpServers": {
    "corveil": {
      "transport": {
        "type": "http",
        "url": "https://your-corveil-host/mcp",
        "headers": {
          "X-Corveil-Key": "sk-citadel-your-key-here"
        }
      }
    }
  }
}

Codex CLI (~/.codex/config.toml)

[mcp_servers.corveil]
url = "https://your-corveil-host/mcp"
http_headers = { "X-Corveil-Key" = "sk-citadel-your-key-here" }

Verify

curl -sS https://your-corveil-host/mcp \
  -H "X-Corveil-Key: sk-citadel-your-key-here" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

---

For everything else — the two auth methods (API key and OAuth/DCR), the three tool namespaces and which credential class receives each, ?ns= narrowing, the full tool catalog (ontology_*, insights_*, control_*), rate limits, and troubleshooting — see the Corveil MCP reference.

To govern external MCP servers (GitHub, AWS, …) behind Corveil instead of connecting to Corveil's own tools, see the MCP Gateway.