勇敢搜索MCP

Usage with ChatGPT

The Brave Search MCP Server can be used with the web UI of ChatGPT. It takes a few steps.

1. Enable Developer Mode in ChatGPT

Settings → Apps → Advanced settings → Developer mode

Additional instructions here

2. Run the Brave Search MCP in HTTP mode and UI mode

BRAVE_API_KEY="your_key_here" npx -y brave-search-mcp --http --ui

3. Create a local tunnel to expose the MCP Server to ChatGPT

Sign up and configure ngrok, the free plan works.

ngrok http 3001

Take note of the forwarding URL.

...
Forwarding                    https://john-joe-asdf.ngrok-free.dev -> http://localhost:3001
...

4. Add Brave Search MCP as a Connector to ChatGPT

Open ChatGPT Apps settings

Click Apps

Click Create Apps

Fill out the form using the URL from step 3 as the MCP Server URL, but add /mcp.

https://john-joe-asdf.ngrok-free.dev/mcp

For Authentication, select 'No Auth'

Tick the checkbox for 'I understand and want to continue'

Then click Create.

5. Using the Brave Search MCP Server

In the ChatGPT UI, click the '+' button, scroll to '...more', select the newly created Brave Search app, and enter your query.

Usage with Claude Code

For Claude Code users, run this command:

Windows:

claude mcp add-json brave-search '{"command":"cmd","args":["/c","npx","-y","brave-search-mcp"],"env":{"BRAVE_API_KEY":"YOUR_API_KEY_HERE"}}'

Linux/macOS:

claude mcp add-json brave-search '{"command":"npx","args":["-y","brave-search-mcp"],"env":{"BRAVE_API_KEY":"YOUR_API_KEY_HERE"}}'

Replace YOUR_API_KEY_HERE with your actual Brave Search API key.

Usage with Claude Desktop

MCP Bundle (MCPB)

1. Download the mcpb file from the Releases 2. Open it with Claude Desktop or Go to File -> Settings -> Extensions and drag the .mcpb file to the window to install it

Docker

1. Clone the repo
2. Build the image from the repo root

docker build -t brave-search-mcp:latest -f apps/brave-search-mcp/Dockerfile .

1. Run it directly if you want HTTP mode:

docker run --rm -p 3001:3001 -e BRAVE_API_KEY="YOUR_API_KEY_HERE" brave-search-mcp:latest --http

1. Add this to your claude_desktop_config.json for stdio mode:

{
  "mcp-servers": {
    "brave-search": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BRAVE_API_KEY",
        "brave-search-mcp"
      ],
      "env": {
        "BRAVE_API_KEY": "YOUR API KEY HERE"
      }
    }
  }
}

NPX

Add this to your claude_desktop_config.json:

{
  "mcp-servers": {
    "brave-search": {
      "command": "npx",
      "args": [
        "-y",
        "brave-search-mcp"
      ],
      "env": {
        "BRAVE_API_KEY": "YOUR API KEY HERE"
      }
    }
  }
}

Usage with LibreChat

Add this to librechat.yaml

brave-search:
  command: sh
  args:
    - -c
    - BRAVE_API_KEY=API KEY npx -y brave-search-mcp

Configuration

Environment-only settings

These settings are always read from the process environment, regardless of mode:

• BRAVE_API_KEY (required): Brave Search API key.
• PORT (optional): HTTP port (default: 3001).
• HOST (optional): Interface to bind to (default: 0.0.0.0).
• BRAVE_MCP_CONFIG (optional): Absolute or relative path to a TOML config file for feature settings.

Env mode feature settings

When BRAVE_MCP_CONFIG is not set, these feature env vars are supported:

• ALLOWED_HOSTS (HTTP mode only): Comma-separated list of allowed hostnames for Host header validation.
• Example: ALLOWED_HOSTS=localhost,127.0.0.1,my-app.ngrok-free.app
• Use hostnames only (no scheme/path), e.g. my-app.ngrok-free.app not https://my-app.ngrok-free.app/mcp
• BRAVE_MCP_POLICY_FILE: JSON policy file path.
• BRAVE_MCP_POLICY_REDACT: true to redact matched text instead of blocking it.
• BRAVE_MCP_REQUEST_LIMIT: Positive integer request cap.
• BRAVE_MCP_WINDOW_SECONDS: Non-negative integer rolling window size.
• BRAVE_MCP_COOLDOWN_SECONDS: Non-negative integer cooldown after the limit is exceeded.
• BRAVE_MCP_AUDIT_LOG: true to emit audit logs.
• BRAVE_MCP_AUDIT_LOG_RAW: true to include raw query text in audit logs.
• BRAVE_MCP_REQUIRE_JUSTIFICATION: true to reject tool calls without a justification string.

Examples:

```bash

File mode (`BRAVE_MCP_CONFIG`)

When BRAVE_MCP_CONFIG is set, the file controls feature configuration, including the HTTP host allowlist.

[auth]
httpApiKey = "sk-..."
requireAuth = true
callerId = "team-a"

[auth.jwt]
jwksUri = "https://idp.example.com/.well-known/jwks.json"
audience = "brave-search-mcp"
clockSkewSeconds = 30

[auth.oauth]
issuer = "https://idp.example.com"
audience = "brave-search-mcp"
clientId = "client-123"
clientSecret = "super-secret"
verifyStrategy = "jwks"

[audit]
enabled = true
logRaw = false
hmacSecret = "audit-secret"

[policy]
file = "/etc/brave-mcp/policy.json"
redact = false

[guardrail]
requestLimit = 100
windowSeconds = 60
cooldownSeconds = 10
requireJustification = false

[server]
allowedHosts = [
  "localhost",
  "127.0.0.1",
  "my-app.ngrok-free.app",
]

Notes:

• BRAVE_API_KEY, PORT, and HOST remain environment-only even in file mode.
• If you set overlapping feature env vars such as BRAVE_MCP_REQUEST_LIMIT or ALLOWED_HOSTS alongside BRAVE_MCP_CONFIG, startup warns that they are being ignored.
• Unknown TOML keys also emit warnings so typos like [guardrails] are visible before you debug runtime behavior.

To validate a config file without starting the server, use the packaged entrypoint after building the app workspace:

pnpm -C apps/brave-search-mcp run build
node apps/brave-search-mcp/dist/index.js --check-config ./apps/brave-search-mcp/test/fixtures/config.valid.toml

To run the built local entrypoint in file mode:

pnpm -C apps/brave-search-mcp run build
BRAVE_API_KEY="your_key_here" BRAVE_MCP_CONFIG="$PWD/apps/brave-search-mcp/test/fixtures/config.valid.toml" node apps/brave-search-mcp/dist/index.js --http

Getting an API Key

1. Sign up for a Brave Search API account
2. Choose a plan
3. Generate your API key from the developer dashboard