Skip to content
mcp/harbor

Gemini CLI Linked API check_connection_status

How to: Gemini CLI Linked API check_connection_status

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

Add Linked API to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "linkedapi-mcp": {
      "httpUrl": "https://mcp.linkedapi.io/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

Linked API will not start until these are set, so check_connection_status never becomes available.

  • LINKED_API_TOKEN
  • IDENTIFICATION_TOKEN

Same tool, other clients

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

Linked API MCP server