Skip to content

Grok Brave Search brave_web_search

How to: Grok Brave Search brave_web_search

client:Grok transport:stdio tool:brave_web_search

Add Brave Search to Grok

  1. 01

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

{
  "mcpServers": {
    "brave-search": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@brave/brave-search-mcp-server"
      ],
      "env": {
        "BRAVE_API_KEY": "<BRAVE_API_KEY>"
      }
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

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

  3. 04

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

Brave Search will not start until these are set, so brave_web_search never becomes available.

  • BRAVE_API_KEY

Same tool, other clients

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.