Skip to content

Grok Kellian kellian_batch_get_trading_rules

How to: Grok Kellian kellian_batch_get_trading_rules

client:Grok transport:streamable-http tool:kellian_batch_get_trading_rules

Add Kellian to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "kellian": {
      "type": "http",
      "url": "https://mcp.kellian.app"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that Kellian's identifier in your config matches the one above exactly.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Set these first

Kellian will not start until these are set, so kellian_batch_get_trading_rules never becomes available.

  • KELLIAN_API_KEY

Same tool, other clients

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