Skip to content

Gemini CLI mitre cwe mcp server cwe_list_reference

How to: Gemini CLI mitre cwe mcp server cwe_list_reference

client:Gemini CLI transport:streamable-http tool:cwe_list_reference

Add mitre cwe mcp server to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "mitre-cwe-mcp-server": {
      "httpUrl": "https://mitre-cwe.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something cwe_list_reference does. Gemini CLI lists the server's tools on connect and calls cwe_list_reference itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that mitre cwe mcp server's identifier in your config matches the one above exactly.

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

mitre cwe mcp server will not start until these are set, so cwe_list_reference never becomes available.

  • MCP_LOG_LEVEL
  • CWE_CACHE_DIR

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.