Skip to content

Gemini CLI TensorFeed submit_wantlist_item

How to: Gemini CLI TensorFeed submit_wantlist_item

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

Add TensorFeed to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "mcp-server": {
      "httpUrl": "https://mcp.tensorfeed.ai/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

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

TensorFeed will not start until these are set, so submit_wantlist_item never becomes available.

  • TENSORFEED_TOKEN

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.