Skip to content
mcp/harbor

Gemini CLI Diogenes Gateway agent_schema_enforcer

How to: Gemini CLI Diogenes Gateway agent_schema_enforcer

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

Add Diogenes Gateway to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "diogenes-gateway": {
      "httpUrl": "https://diogenes-l402-gateway.corinth.workers.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that Diogenes Gateway'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 18 October 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.

Diogenes Gateway MCP server