Skip to content
mcp/harbor

Gemini CLI milestone schedule delivery_schedule_document

How to: Gemini CLI milestone schedule delivery_schedule_document

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

Add milestone schedule to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "milestone-schedule": {
      "httpUrl": "https://mcp.zovo.one/mcp/milestone-schedule"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that milestone schedule'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

milestone schedule will not start until these are set, so delivery_schedule_document never becomes available.

  • MCP_LICENSE_KEY

Same tool, other clients

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

milestone schedule MCP server