Skip to main content
mcpSource-backed
Brave Search logo

Brave Search MCP Server

Official Brave Search MCP server for giving Claude web, local, place, image, video, news, LLM context, and summarizer search tools backed by the Brave Search API.

by Brave Software · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/brave/brave-search-mcp-server#readme, https://github.com/brave/brave-search-mcp-server, https://brave.com/search/api/
Brand
Brave Search
Brand domain
brave.com
Brand asset source
brandfetch
Safety notes
Brave Search MCP uses BRAVE_API_KEY from the MCP client environment or command-line options., The server defaults to stdio transport in version 2.x and can also run an HTTP transport when explicitly configured., Tools can send web, news, image, video, local, place, and LLM-context queries to the Brave Search API., Local and place tools may use location strings, coordinates, postal codes, or optional location headers., Summarizer workflows depend on summary keys returned by web search and should be checked against cited source URLs., API usage may be metered or plan-limited, especially for Pro-only local search capabilities and extra snippets.
Privacy notes
Search queries, location parameters, result filters, language settings, freshness windows, and optional headers may reveal user intent, location, research topics, or sensitive business context., BRAVE_API_KEY should stay out of prompts, issues, logs, screenshots, and committed files., Returned snippets, summaries, search results, local-business metadata, images, videos, and news items can include third-party copyrighted or sensitive content., HTTP transport should be bound and exposed carefully so the API key and search tools are not reachable by untrusted clients.
Author
Brave Software
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/5 ready
Account & credentials1Install & runtime2Review & approval210 minutes

Safety & privacy surface

Safety & privacy surface

6 safety and 4 privacy notes across 6 risk areas. Review closely: credentials & tokens, network access, third-party handling.

6 areas
  • SafetyExecution & processesBrave Search MCP uses BRAVE_API_KEY from the MCP client environment or command-line options.
  • SafetyNetwork accessThe server defaults to stdio transport in version 2.x and can also run an HTTP transport when explicitly configured.
  • SafetyGeneralTools can send web, news, image, video, local, place, and LLM-context queries to the Brave Search API.
  • SafetyGeneralLocal and place tools may use location strings, coordinates, postal codes, or optional location headers.
  • SafetyGeneralSummarizer workflows depend on summary keys returned by web search and should be checked against cited source URLs.
  • SafetyGeneralAPI usage may be metered or plan-limited, especially for Pro-only local search capabilities and extra snippets.
  • PrivacyGeneralSearch queries, location parameters, result filters, language settings, freshness windows, and optional headers may reveal user intent, location, research topics, or sensitive business context.
  • PrivacyLocal filesBRAVE_API_KEY should stay out of prompts, issues, logs, screenshots, and committed files.
  • PrivacyThird-party handlingReturned snippets, summaries, search results, local-business metadata, images, videos, and news items can include third-party copyrighted or sensitive content.
  • PrivacyCredentials & tokensHTTP transport should be bound and exposed carefully so the API key and search tools are not reachable by untrusted clients.

Safety notes

  • Brave Search MCP uses BRAVE_API_KEY from the MCP client environment or command-line options.
  • The server defaults to stdio transport in version 2.x and can also run an HTTP transport when explicitly configured.
  • Tools can send web, news, image, video, local, place, and LLM-context queries to the Brave Search API.
  • Local and place tools may use location strings, coordinates, postal codes, or optional location headers.
  • Summarizer workflows depend on summary keys returned by web search and should be checked against cited source URLs.
  • API usage may be metered or plan-limited, especially for Pro-only local search capabilities and extra snippets.

Privacy notes

  • Search queries, location parameters, result filters, language settings, freshness windows, and optional headers may reveal user intent, location, research topics, or sensitive business context.
  • BRAVE_API_KEY should stay out of prompts, issues, logs, screenshots, and committed files.
  • Returned snippets, summaries, search results, local-business metadata, images, videos, and news items can include third-party copyrighted or sensitive content.
  • HTTP transport should be bound and exposed carefully so the API key and search tools are not reachable by untrusted clients.

Prerequisites

  • Brave Search API account and API key.
  • Node.js and npm available in the MCP client runtime.
  • API plan review for web, local, extra snippets, summarizer, and LLM context usage.
  • Tool whitelist or blacklist if the client should expose only selected search tools.
  • Privacy review for search queries, location inputs, query freshness, and returned result metadata.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "brave-search": {
      "command": "npx",
      "args": ["-y", "@brave/brave-search-mcp-server", "--transport", "stdio"],
      "env": {
        "BRAVE_API_KEY": "<your-brave-search-api-key>"
      }
    }
  }
}

About this resource

Content

Brave Search MCP Server is Brave's official Model Context Protocol server for the Brave Search API. It gives Claude and other MCP clients access to web search, local search, place search, image search, video search, news search, LLM-context retrieval, and summarizer tools.

Version 2.x defaults to stdio transport to match common MCP client conventions. HTTP transport remains available when configured with an environment variable or runtime argument. The server requires a Brave Search API key.

Source Review

These sources were reviewed on 2026-06-06. Prefer the Brave Search API page, repository README, MCP metadata, package metadata, and license for current setup commands, tool names, transport behavior, API key requirements, and plan limitations.

Features

  • Official MCP server from brave/brave-search-mcp-server.
  • Stdio transport by default, with optional HTTP transport.
  • NPM package @brave/brave-search-mcp-server.
  • Required BRAVE_API_KEY environment variable.
  • Web search with country, language, result count, freshness, safe search, result filters, goggles, and summary-key options.
  • Local business search and place search with location-aware parameters.
  • Image, video, and news search tools.
  • LLM-context retrieval for RAG and grounded agent workflows.
  • Summarizer tool for AI-powered summaries based on summary keys.
  • Tool whitelist and blacklist controls through environment variables or command-line options.
  • Docker and VS Code installation examples in the README.

Installation

For local stdio usage, configure an MCP client with the official npm package and provide a Brave Search API key:

{
  "mcpServers": {
    "brave-search": {
      "command": "npx",
      "args": ["-y", "@brave/brave-search-mcp-server", "--transport", "stdio"],
      "env": {
        "BRAVE_API_KEY": "<your-brave-search-api-key>"
      }
    }
  }
}

To run HTTP transport instead, follow the README's BRAVE_MCP_TRANSPORT or --transport http guidance and bind the server only where trusted clients can reach it.

Use Cases

  • Ground Claude answers with current Brave web search results.
  • Retrieve LLM-optimized context for a research query.
  • Search current news with freshness controls.
  • Look up places, local businesses, ratings, hours, and contact metadata.
  • Compare image or video search results before selecting sources.
  • Generate a summary from a Brave web-search summary key.
  • Restrict an MCP client to only web search or LLM-context tools through tool whitelisting.
  • Use safe-search, country, language, and freshness options for repeatable research workflows.

Safety and Privacy

Search MCP servers are read-only in the sense that they do not mutate a local project, but they still send user intent and sometimes location context to a third-party API. Treat queries as potentially sensitive, especially for product research, investigations, legal questions, medical topics, security research, or people-search workflows.

Keep BRAVE_API_KEY secret, review plan limits before high-volume agent loops, and require source citation review before trusting generated summaries. If using HTTP transport, bind it carefully and avoid exposing the server to untrusted networks or clients.

Duplicate Check

No Brave Search MCP Server, brave/brave-search-mcp-server, @brave/brave-search-mcp-server, or Brave Search API MCP entry was found in content/mcp, content/tools, content/guides, content/agents, or content/skills.

Source citations

Add this badge to your README

Show that Brave Search MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/brave-search-mcp-server.svg)](https://heyclau.de/entry/mcp/brave-search-mcp-server)

How it compares

Brave Search MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Official Brave Search MCP server for giving Claude web, local, place, image, video, news, LLM context, and summarizer search tools backed by the Brave Search API.

Open dossier

No-key multi-engine MCP server, CLI, and local daemon for web search and public web content retrieval across engines such as Bing, DuckDuckGo, Brave, Exa, Baidu, CSDN, Juejin, Startpage, and Sogou.

Open dossier

AgentQL MCP server for extracting structured JSON from public webpages using a URL and natural-language extraction prompt.

Open dossier

MCP server that connects Claude to Bright Data web search, scraping, browser automation, public web datasets, and package metadata tools.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitteroktofeesh1oktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandBrave Search logoBrave SearchAgentQL logoAgentQLBright Data logoBright Data
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorBrave SoftwareAas-eeAgentQLBright Data
Added2026-06-062026-06-062026-06-062026-06-05
Platforms
Harness
Source repo
Safety notesBrave Search MCP uses BRAVE_API_KEY from the MCP client environment or command-line options. The server defaults to stdio transport in version 2.x and can also run an HTTP transport when explicitly configured. Tools can send web, news, image, video, local, place, and LLM-context queries to the Brave Search API. Local and place tools may use location strings, coordinates, postal codes, or optional location headers. Summarizer workflows depend on summary keys returned by web search and should be checked against cited source URLs. API usage may be metered or plan-limited, especially for Pro-only local search capabilities and extra snippets.open-webSearch can send search queries to multiple public engines and fetch public web pages, GitHub READMEs, CSDN articles, Juejin articles, and other supported targets. Search and fetch results can be incomplete, stale, rate-limited, blocked, region-dependent, or affected by search-engine ranking and scraping protections. Respect each target site's terms and robots expectations; do not use the server for abusive scraping, credentialed browsing, paywall bypass, or personal-data harvesting. The optional local daemon exposes HTTP endpoints for local tooling; keep it bound to trusted local interfaces and do not treat it as a public internet API. Proxy settings, Playwright WebSocket/CDP endpoints, and reused browser sessions can route traffic or cookies through external systems; configure them deliberately. Leave TLS verification enabled unless a specific target has a broken certificate chain and the risk has been accepted.AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API. The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited. Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns. The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies. Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.This server sends web searches, URLs, scraping targets, browser actions, package names, and dataset requests to Bright Data APIs. Review website terms, robots policies, rate limits, jurisdictional requirements, and internal scraping policies before automating collection. `PRO_MODE`, browser automation groups, data-product groups, and batch tools can increase cost, request volume, and operational impact. The server can create or use Bright Data zones through API calls; review account permissions and zone settings before running it with broad API tokens. Use `RATE_LIMIT`, group selection, and explicit tool allowlists to keep agent-driven browsing and scraping bounded.
Privacy notesSearch queries, location parameters, result filters, language settings, freshness windows, and optional headers may reveal user intent, location, research topics, or sensitive business context. BRAVE_API_KEY should stay out of prompts, issues, logs, screenshots, and committed files. Returned snippets, summaries, search results, local-business metadata, images, videos, and news items can include third-party copyrighted or sensitive content. HTTP transport should be bound and exposed carefully so the API key and search tools are not reachable by untrusted clients.Search queries, fetched URLs, result titles, snippets, article content, proxy URLs, browser endpoints, and fetched page text can be exposed to MCP clients, logs, and model context. Live search engines and fetched websites may observe queries, IP address, proxy exit, browser fingerprints, cookies, timing, and request headers. Playwright fallback or CDP reuse can expose browser state, existing cookies, logged-in sessions, or verification state to fetched pages. The project includes public URL validation and private-network target protections, but operators should still avoid fetching internal, secret, or customer-specific URLs. Redact sensitive search terms and downloaded page content before sharing transcripts or logs.Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API. Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material. AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files. Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.Bright Data API tokens must stay in environment variables or secret managers and should never be committed to MCP configuration files. Queries, URLs, package names, web pages, scraping outputs, dataset filters, and browser activity may be visible to Bright Data, the MCP client, and the model provider. Public web data can still contain personal data, copyrighted content, customer information, or contractual restrictions. Tool outputs can include scraped page text, search results, social or ecommerce dataset fields, package metadata, and browser screenshots depending on enabled tools.
Prerequisites
  • Brave Search API account and API key.
  • Node.js and npm available in the MCP client runtime.
  • API plan review for web, local, extra snippets, summarizer, and LLM context usage.
  • Tool whitelist or blacklist if the client should expose only selected search tools.
  • Node.js 18 or newer for the published npm package.
  • Review of search-engine terms, scraping limits, rate limits, and allowed use for the target websites.
  • Optional proxy configuration only when live search or fetch traffic must route through an approved proxy.
  • Optional Playwright or browser endpoint setup only when request-based search/fetch is insufficient.
  • Node.js and npx available to the MCP client runtime.
  • AgentQL API key from the AgentQL developer portal.
  • Approved list of public webpages or domains Claude may query.
  • Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.
  • Node.js and npx available to the MCP client runtime.
  • Bright Data account and API token stored as `API_TOKEN`.
  • Review of Bright Data plan limits, free-tier scope, paid modes, and data-product terms.
  • A decision about whether to use default rapid tools, `PRO_MODE`, `GROUPS`, or explicit `TOOLS`.
Install
npx -y @brave/brave-search-mcp-server --transport stdio
npx -y open-websearch@latest
npx -y agentql-mcp
npx @brightdata/mcp
Config
{
  "mcpServers": {
    "brave-search": {
      "command": "npx",
      "args": ["-y", "@brave/brave-search-mcp-server", "--transport", "stdio"],
      "env": {
        "BRAVE_API_KEY": "<your-brave-search-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "open-websearch": {
      "command": "npx",
      "args": [
        "-y",
        "open-websearch@latest"
      ],
      "env": {
        "MODE": "stdio",
        "DEFAULT_SEARCH_ENGINE": "duckduckgo",
        "ALLOWED_SEARCH_ENGINES": "duckduckgo,startpage,bing",
        "NPM_CONFIG_IGNORE_SCRIPTS": "true"
      },
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "agentql": {
      "command": "npx",
      "args": ["-y", "agentql-mcp"],
      "env": {
        "AGENTQL_API_KEY": "<your-agentql-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "bright-data": {
      "command": "npx",
      "args": ["@brightdata/mcp"],
      "env": {
        "API_TOKEN": "YOUR_BRIGHT_DATA_API_TOKEN",
        "GROUPS": "code,research",
        "RATE_LIMIT": "100/1h"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.