Skip to content

Gemini CLI interpro mcp server interpro_get_protein_domains

How to: Gemini CLI interpro mcp server interpro_get_protein_domains

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

Add interpro mcp server to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "interpro-mcp-server": {
      "httpUrl": "https://interpro.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

interpro mcp server will not start until these are set, so interpro_get_protein_domains never becomes available.

  • MCP_LOG_LEVEL
  • INTERPRO_SCAN_EMAIL

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.