Skip to content
mcp/harbor

Gemini CLI McpStamp Timer Tracking entry_log

How to: Gemini CLI McpStamp Timer Tracking entry_log

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

Add McpStamp Timer Tracking to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "timer-tracking": {
      "httpUrl": "https://mcp.zovo.one/mcp/timer-tracking"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

McpStamp Timer Tracking will not start until these are set, so entry_log 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 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.

McpStamp Timer Tracking MCP server