Skip to content
mcp/harbor

Gemini CLI Uphealth Signal Prompt/evaluate_signal

How to: Gemini CLI Uphealth Signal evaluate_signal

client:Gemini CLI transport:streamable-http prompt:evaluate_signal

Add Uphealth Signal to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "mcp": {
      "httpUrl": "https://mcp.uphealth.us/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    evaluate_signal 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.

  3. 04

    If it does not appear, check that Uphealth Signal 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

Set these first

Uphealth Signal will not start until these are set, so it never reaches Gemini CLI.

  • UPHEALTH_API_KEY

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.

Uphealth Signal MCP server