Skip to content
mcp/harbor

Gemini CLI Data Breach Notification Deadlines who_to_notify

How to: Gemini CLI Data Breach Notification Deadlines who_to_notify

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

Add Data Breach Notification Deadlines to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "breach-notification-deadlines": {
      "httpUrl": "https://breach-notification-deadlines.nerolabs.workers.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that Data Breach Notification Deadlines'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

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.

Data Breach Notification Deadlines MCP server