Skip to main content
Glama
deenesjakoruzh
kwp-lab

Brave Search With Proxy

by kwp-lab
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

Brave Search MCP Server

An MCP server leveraging the Brave Search API for web and local search, with optional HTTP proxy configuration.

This repository forks from the Model Context Protocol servers and replaces the native fetch implementation with the library node-fetch-native.

The server will use the http_proxy and https_proxy environment variables to route requests through the proxy server by default if they are set. You also can set the BRAVE_SEARCH_PROXY environment variable to use a different proxy server.

Features

  • Web Search: General queries, news, articles, with pagination and freshness controls

  • Local Search: Find businesses, restaurants, and services with detailed information

  • Flexible Filtering: Control result types, safety levels, and content freshness

  • Smart Fallbacks: Local search automatically falls back to web when no results are found

Related MCP server: MCP2Brave

Tools

  • brave_web_search

    • Execute web searches with pagination and filtering

    • Inputs:

      • query (string): Search terms

      • count (number, optional): Results per page (max 20)

      • offset (number, optional): Pagination offset (max 9)

  • brave_local_search

    • Search for local businesses and services

    • Inputs:

      • query (string): Local search terms

      • count (number, optional): Number of results (max 20)

    • Automatically falls back to web search if no local results found

Configuration

Getting an API Key

  1. Sign up for a Brave Search API account

  2. Choose a plan (Free tier available with 2,000 queries/month)

  3. Generate your API key from the developer dashboard

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

Docker

{
  "mcpServers": {
    "brave-search": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BRAVE_API_KEY",
        "mcp/brave-search"
      ],
      "env": {
        "BRAVE_API_KEY": "YOUR_API_KEY_HERE",
        "BRAVE_SEARCH_PROXY": "https://example.com:10890" // Optional, remove if not needed
      }
    }
  }
}

NPX

{
  "mcpServers": {
    "brave-search": {
      "command": "npx",
      "args": [
        "-y",
        "@kwp-lab/mcp-brave-search"
      ],
      "env": {
        "BRAVE_API_KEY": "YOUR_API_KEY_HERE",
        "BRAVE_SEARCH_PROXY": "https://example.com:10890" // Optional, remove if not needed
      }
    }
  }
}

Usage with VS Code

For quick installation, use the one-click installation buttons below...

Install with NPX in VS Code Install with NPX in VS Code Insiders

Install with Docker in VS Code Install with Docker in VS Code Insiders

For manual installation, add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).

Optionally, you can add it to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others.

Note that the mcp key is not needed in the .vscode/mcp.json file.

Docker

{
  "mcp": {
    "inputs": [
      {
        "type": "promptString",
        "id": "brave_api_key",
        "description": "Brave Search API Key",
        "password": true
      }
    ],
    "servers": {
      "brave-search": {
        "command": "docker",
        "args": [
          "run",
          "-i",
          "--rm",
          "-e",
          "BRAVE_API_KEY",
          "mcp/brave-search"
        ],
        "env": {
          "BRAVE_API_KEY": "${input:brave_api_key}",
          "BRAVE_SEARCH_PROXY": "https://example.com:10890" // Optional, remove if not needed
        }
      }
    }
  }
}

NPX

{
  "mcp": {
    "inputs": [
      {
        "type": "promptString",
        "id": "brave_api_key",
        "description": "Brave Search API Key",
        "password": true
      }
    ],
    "servers": {
      "brave-search": {
        "command": "npx",
        "args": ["-y", "@kwp-lab/mcp-brave-search"],
        "env": {
          "BRAVE_API_KEY": "${input:brave_api_key}",
          "BRAVE_SEARCH_PROXY": "https://example.com:10890" // Optional, remove if not needed
        }
      }
    }
  }
}

Build

Docker build:

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

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

2 tools

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • First observedbrave_local_search
    • First observedbrave_web_search
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: brave_local_search targets local businesses and physical locations with 'near me' queries, while brave_web_search handles general web searches for information, news, and online content. There is no overlap in functionality, as each tool is specialized for different query types and data sources, making it easy for an agent to choose the correct one based on the user's intent.

Naming Consistency5/5

Both tool names follow a consistent pattern: 'brave_' prefix followed by a descriptive term ('local_search' and 'web_search') using snake_case. This naming convention clearly indicates the server domain (Brave Search) and the specific search type, making the tools predictable and easy to understand without any deviations or mixed styles.

Tool Count3/5

With only 2 tools, the server feels thin for a search domain, as it might benefit from additional tools like image search, news search, or advanced filtering options. However, the tools cover the core local and web search functionalities adequately, so it's borderline but not severely lacking. A typical search server would have more tools to handle diverse query types and result formats.

Completeness4/5

The server covers the essential search operations for local and web queries, with each tool providing detailed capabilities like pagination, filtering, and fallback mechanisms. Minor gaps exist, such as no dedicated tools for image or video searches, but agents can work around this using the web search tool. The surface is reasonably complete for basic search needs without significant dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Brave Search MCP Server

    Shoofio
    A
    license
    Not graded
    quality
    F
    maintenance
    An MCP server that integrates the Brave Search API to provide both web and local search capabilities, with features like pagination, filtering, and smart fallbacks.
    15
    MIT

  • Brave Search MCP

    mikechao
    A
    license
    A
    quality
    D
    maintenance
    An MCP Server implementation that integrates the Brave Search API, providing, Web Search, Local Points of Interest Search, Image Search, Video Search, News Search and LLM Context Search capabilities
    5
    196
    125
    GPL 3.0