Skip to content
Menu

MCP server / search / source-linked

Brave Search MCP

Brave Search MCP for web, local, image, video and news search. It is a discovery layer rather than a page extraction or browser-control layer, so pair it with a fetcher when the answer must quote primary documents. Keep the query, filters and selected result URLs in the research record.

Before you choose.

Identify the implementation and the job it supports.

Which implementation is this?
Brave Search MCP for web, local, image, video and news search. It is a discovery layer rather than a page extraction or browser-control layer, so pair it with a fetcher when the answer must quote primary documents. Keep the query, filters and selected result URLs in the research record.
Implementation source ↗

Brave Search MCP for web, local, image, video and news search. It is a discovery layer rather than a page extraction or browser-control layer, so pair it with a fetcher when the answer must quote primary documents. Keep the query, filters and selected result URLs in the research record.

Setup and connection.

The documented interface, authentication and installation path.

Connection / transport
stdio default; HTTP optional
Authentication
BRAVE_API_KEY

Use the official endpoint/package, store secrets outside committed config, and review returned tools before use.

Setup reference ↗

Documented setup example. Review the source and credentials before running; this command was not executed for this article.

npx -y @brave/brave-search-mcp-server --transport stdio

What it actually exposes.

Concrete capabilities with maintainer sources.

Documented capability / 01

Primary capability

Web queries with freshness and language filters

Documentation ↗
Documented capability / 02

Secondary capability

Local search has Pro-plan fallback

Documentation ↗
Documented capability / 03

Workflow fit

Choose by transport, auth and state needs.

Documentation ↗

Evidence and method.

What was checked and what was not tested.

WHO

Editorial record

Compiled by clawbot.ai.

HOW

Source method

Public maintainer documentation and repositories. This is not a hands-on product review.

WHEN

Last checked 2026-10-01

Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.

Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.

Try a specific task.

A bounded evaluation you can reproduce in your own environment.

Proposed decision workflow (proposed; not tested)

Suggested evaluation, not an observed test result.

  1. Choose a bounded public test task.
  2. Record setup, tool calls and source URLs.
  3. Review result, cost and failure boundaries.

What to inspect: Suggested evaluation; not tested.

Workflow reference ↗

Permissions and limitations.

Read these constraints before granting access.

Decide by workflow.

Make the expected output explicit before you connect.

Suggested evaluation; not tested.

Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.

Compare the alternatives.

Specific reasons to choose another route, with the tradeoff shown.

Editorial decision guidance inferred from the linked documentation; no quality or speed benchmark.
AlternativeChoose it whenTradeoff
Tavily MCPEditorial inference: you need a different workflow.Compare transport, auth and state tradeoffs.
Documentation ↗
Exa MCPEditorial inference: you need another workflow.Compare scope and operational tradeoffs.
Documentation ↗

Questions before setup.

Answers specific to this implementation.

What should I verify first?

Confirm current endpoint, auth and returned tools.
Documentation ↗

Is this page a test result?

No; the workflow is a proposed editorial comparison.
Documentation ↗

Source trail.

Maintainer documentation used in this record.