Skip to content

Gemini CLI cisa cybersecurity mcp server Resource/ICSA-26-260-03 — Hitachi Energy FACTS Control Platform (FCP)

How to: Gemini CLI cisa cybersecurity mcp server ICSA-26-260-03 — Hitachi Energy FACTS Control Platform (FCP)

client:Gemini CLI transport:streamable-http resource:ICSA-26-260-03 — Hitachi Energy FACTS Control Platform (FCP)

Add cisa cybersecurity mcp server to Gemini CLI

  1. 01

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

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

    Save the file and restart Gemini CLI.

  2. 03

    ICSA-26-260-03 — Hitachi Energy FACTS Control Platform (FCP) 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 cisa cybersecurity mcp server 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

cisa cybersecurity mcp server will not start until these are set, so it never reaches Gemini CLI.

  • MCP_LOG_LEVEL
  • CISA_KEV_REFRESH_CRON
  • CISA_CSAF_MIRROR_PATH
  • CISA_CSAF_MIRROR_AUTO_INIT
  • CISA_CSAF_REFRESH_CRON
  • CISA_VULNRICHMENT_CACHE_TTL_SECONDS
  • CISA_FEED_CACHE_TTL_SECONDS
  • CISA_HTTP_TIMEOUT_MS

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.