Brave Search

Created By
Brave10 months ago
An MCP server implementation that integrates the Brave Search API, providing comprehensive search capabilities including web search, local business search, image search, video search, news search, and AI-powered summarization. This project supports both HTTP and STDIO transports, with HTTP as the default mode.
Overview

Brave Search is an MCP server implementation that integrates the Brave Search API, offering comprehensive search capabilities including web, local business, image, video, and news searches, along with AI-powered summarization.

To use Brave Search, set up the server with your Brave Search API key and choose your preferred transport mode (HTTP or STDIO). You can then perform various types of searches using the provided tools.

  • Comprehensive web search with rich results and advanced filtering options.
  • Local business search with detailed information.
  • Video and image search with metadata and thumbnail support.
  • News search with freshness controls.
  • AI-powered summarization of search results.
  1. Finding local businesses and services.
  2. Searching for videos and images with specific criteria.
  3. Keeping up with current news articles.
  4. Generating summaries from search results for quick insights.
  • What types of searches can I perform?

    You can perform web, local, image, video, and news searches.

  • Is there a limit on the number of queries?

    Yes, the free plan allows 2,000 queries per month, while the Pro plan offers enhanced features.

  • How do I get an API key?

    Sign up for a Brave Search API account and generate your API key from the developer dashboard.

Server Config

{
  "mcpServers": {
    "brave-search": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BRAVE_API_KEY",
        "mcp/brave-search"
      ],
      "env": {
        "BRAVE_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
Brave
Star
-
Language
-
License
-
Category
search

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago