Skip to content

Gemini CLI Claidex MCP Resource/metrics

How to: Gemini CLI Claidex MCP metrics

client:Gemini CLI transport:streamable-http resource:metrics

Add Claidex MCP to Gemini CLI

  1. 01

    Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "failure-intelligence": {
      "httpUrl": "https://app.claidex.com/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    metrics is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.

  3. 04

    If it does not appear, check that Claidex MCP is connected and that you are looking at its resources rather than its tools.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

Claidex MCP will not start until these are set, so it never reaches Gemini CLI.

  • CLAIDEX_MCP_URL
  • CLAIDEX_MCP_API_KEY

Same resource, other clients

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.