Skip to content

Gemini CLI cern opendata mcp server cern_opendata_get_records

How to: Gemini CLI cern opendata mcp server cern_opendata_get_records

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

Add cern opendata mcp server to Gemini CLI

  1. 01

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

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

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that cern opendata 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

cern opendata mcp server will not start until these are set, so cern_opendata_get_records never becomes available.

  • MCP_LOG_LEVEL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 2 October 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.