Problem it solves

Claude’s training has a knowledge cutoff. When you ask about a library released six months ago, or a breaking change in a framework update, or why your error message appears in Stack Overflow — Claude is guessing from stale data.

Brave Search MCP gives Claude live web access. It can search for current documentation, look up error messages in real time, check what version of a package is latest, and find answers to questions that postdate its training. This is the difference between an assistant that hedges and one that actually knows.

How to install

First, get a free API key at https://brave.com/search/api. The free tier gives you 2000 queries per month, which is plenty for daily development use.

Then install the MCP server, replacing YOUR_KEY with your actual API key:

Terminal window
claude mcp add --transport stdio --env BRAVE_API_KEY=YOUR_KEY brave-search -- npx -y @brave/brave-search-mcp-server

Note: the old @modelcontextprotocol/server-brave-search package is archived. The current official package is @brave/brave-search-mcp-server.

Restart Claude Code and run /mcp to confirm the server is active.

How to use

Once installed, you can ask Claude to search naturally:

  • “Search for the latest breaking changes in React 19”
  • “Look up this error: ‘Cannot read properties of undefined (reading map)’”
  • “What’s the current latest version of Prisma?”
  • “Find the official docs for the Stripe Checkout API”
  • “Search for how to configure Vite for SSR with Astro”

Claude will run the search, read the results, and incorporate them into its answer — citing sources when useful.

Pro tips

Pair with Fetch MCP. Brave Search finds the right URL; Fetch MCP reads the full page content. Together they give Claude the ability to research any topic end to end: find the relevant docs, read them, then apply them to your code.

Use for dependency audits. Before adding a package, ask: “Search for recent security advisories for [package name].” Claude will surface any known CVEs or deprecation notices.

Error-driven debugging. Copy-paste an exact error message and ask Claude to search for it. You’ll often get the Stack Overflow thread or GitHub issue with the fix faster than you would searching manually.

When NOT to use

Don’t use Brave Search for questions Claude can answer confidently from its training — stable APIs, language fundamentals, well-established patterns. Reserve search queries for things that are time-sensitive or postdate the training cutoff. You only get 2000 free queries per month, so spend them where they matter.