Brave Search MCP Server: Configure and Verify Web Search

Brave publishes an MCP server for its Search API. This guide connects its npm package to VS Code over stdio and gives you a small result-quality check before adding search to a larger workflow.

Docs-derived; sources checked October 17, 2026. MCPFind did not use an API key or perform an authenticated installation for this article.

The directory identifier ai-smithery-brave maps to the official brave/brave-search-mcp-server repository. The identifier is not the npm launch command: this guide uses the official @brave/brave-search-mcp-server package.

Prepare the account and runtime

Obtain an API key through the Brave Search API account setup. Review the current plan and usage limits there; this article does not promise a fixed free allowance or price.

Install Node.js and npm so npx is available to the client. Brave's repository lists Node.js 22 or higher for development and documents the published package, API-key variable, and supported transports. The example below selects stdio explicitly. Official server repository.

Add the VS Code configuration

Create .vscode/mcp.json in your workspace, or merge the following entries into the file if it already exists:

{
  "inputs": [
    {
      "id": "brave-key",
      "type": "promptString",
      "description": "Enter your Brave Search API key",
      "password": true
    }
  ],
  "servers": {
    "brave": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@brave/brave-search-mcp-server", "--transport", "stdio"],
      "env": {
        "BRAVE_API_KEY": "${input:brave-key}"
      }
    }
  }
}

The package, launch arguments, and key variable follow Brave's setup documentation. The servers object, stdio type, and prompted input follow VS Code's MCP reference. Keep the actual key out of the repository.

Inspect the server in VS Code's MCP interface and supply the key when requested. For another client, adapt its configuration format using that client's documentation; do not assume its top-level key or input interpolation matches VS Code.

Check one narrow search

Use brave_web_search for one documentation question whose answer you can independently check. For example, ask for official release documentation for a named product, restrict the date window to the month you are researching, choose the intended country, and request at most three results. Inspect the tool's current parameter schema for the supported date, country, and count values before calling it.

Expected output is a short set of page titles and URLs that match the query and bounds. Open each candidate on the publisher's domain and confirm its publication or update date before citing it. A result snippet is a lead, and a date filter does not establish that the page itself says what the answer claims.

Compare this one task with a browser lookup before adding it to a larger workflow. If results are empty, first confirm that the call succeeded; then consider relaxing one query bound. An authentication error or exhausted quota is a different outcome and should stop the test until the key or account limit is resolved.

If the process cannot start, inspect the npx path and server output. If authentication or quota fails, check the key and account limits before changing the search query. Keep errors separate from “no matching results” in any automation you build.

Add a search integration when it improves a real task. Browse search servers to compare alternatives, and evaluate them on the same questions and source checks rather than an unsupported claim that one provider is always best.