Ask Grok MCP Server

What the code does

We read the source, 4 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const childProcess = spawn(command, safeArgs, {

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      run: sudo apt-get update -qq && sudo apt-get install -y -qq zsh
    - name: Run test batch ${{ matrix.batch }}/5

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add ask-grok -e 'XAI_API_KEY=<XAI_API_KEY>' -- npx -y @ask-llm/grok-mcp

{
  "mcpServers": {
    "ask-grok": {
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/grok-mcp"
      ],
      "env": {
        "XAI_API_KEY": "<XAI_API_KEY>"
      }
    }
  }
}

[mcp_servers.ask-grok]
command = "npx"
args = ["-y", "@ask-llm/grok-mcp"]
env = { XAI_API_KEY = "<XAI_API_KEY>" }

{
  "mcpServers": {
    "ask-grok": {
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/grok-mcp"
      ],
      "env": {
        "XAI_API_KEY": "<XAI_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "ask-grok": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ask-llm/grok-mcp"
      ],
      "env": {
        "XAI_API_KEY": "<XAI_API_KEY>"
      }
    }
  }
}

Put your own value in place of <XAI_API_KEY> (xAI API key used only for requests to https://api.x.ai). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: ASK_GROK_HARNESS (Explicit harness: xai-api (default) or grok-cli; no automatic failover), ASK_GROK_MODEL (Exact selected-harness model override (API default grok-4.7; CLI default grok-4.7; no fallback)), ASK_GROK_REASONING_EFFORT (Reasoning effort: low, medium, high, or xhigh (default: high)), ASK_GROK_MAX_OUTPUT_TOKENS (xAI API output-token ceiling to bound accidental spend (default: 16384)), ASK_GROK_TIMEOUT_MS (Timeout for xAI API requests in milliseconds (default: 600000)), GMCPT_LOG_LEVEL (Log verbosity: debug, info, warn, error (default: warn)).