Gemini CLI coderegistry Prompt/specific-metrics

How to: Gemini CLI coderegistry specific-metrics

client:Gemini CLI transport:streamable-http prompt:specific-metrics

Add coderegistry to Gemini CLI

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

{
  "mcpServers": {
    "coderegistry": {
      "httpUrl": "https://integrator.app.thecoderegistry.com/api/ai/router"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
specific-metrics is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Gemini CLI will not call it for you.
04
If it does not appear, check that coderegistry is connected and that you are looking at its prompts 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

Same prompt, other clients

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, 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 prompt's arguments.

coderegistry MCP server