Skip to content

Gemini CLI MisarMail MCP Server list_integrations

How to: Gemini CLI MisarMail MCP Server list_integrations

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

Add MisarMail MCP Server to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "misarmail-mcp": {
      "httpUrl": "https://api.misar.io/mail/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

MisarMail MCP Server will not start until these are set, so list_integrations never becomes available.

  • MISARMAIL_API_KEY
  • MISARMAIL_BASE_URL

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.