Skip to content

Gemini CLI Algenta MCP Server query_sql_report

How to: Gemini CLI Algenta MCP Server query_sql_report

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

Add Algenta MCP Server to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "algenta": {
      "httpUrl": "https://api.algenta.ai/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

Algenta MCP Server will not start until these are set, so query_sql_report never becomes available.

  • ALGENTA_API_KEY
  • ALGENTA_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.