← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionBrave Search MCP ServerComprehensive Brave Search capabilities through MCPFSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.
FMRS59 / 100 · C66 / 100 · C
Reliability9 / 2010 / 20
Security and permissions14 / 2014 / 20
Maintenance7 / 2015 / 20
Documentation15 / 2015 / 20
Setup experience14 / 2012 / 20
Best for
  • AI agents that need Brave Search API data
  • Workflows requiring web, news, or multimedia search
  • Applications needing structured place and local-business information
  • Developers who want AI clients to directly control the browser
  • Scenarios requiring DOM-level understanding and low-latency automation (50-200 ms)
  • Multi-client support (Claude Code, Cursor, VS Code, etc.)
  • Internal tools or automation scripts needing browser interaction
Not for
  • Offline workflows that do not need an external search service
  • Environments unable to provide a Brave Search API key
  • Users needing full local-search capabilities without a Pro plan
  • Headless browser or server-side monitoring
  • Bypassing website restrictions or unsupervised automation
  • Automation on sensitive pages without human supervision
  • Complex scenarios that require visual understanding (e.g., screenshots)
Required permissions
  • Requires a valid BRAVE_API_KEY, or a key file specified through BRAVE_API_KEY_FILE
  • Requires network access to the Brave Search API
  • In HTTP mode, host binding and port are controlled by configuration
  • Requires installing the Chrome extension, which requests permissions for active tab, debugger, storage, etc.
  • MCP server needs to connect to the extension via WebSocket (default ws://localhost:7225)
  • Optional Streamable HTTP mode requires allowing connections to http://127.0.0.1:7226/mcp
  • Uploading files requires providing absolute local paths
Risks and side effects
  • The API key is a required secret and should not be exposed in logs or shared configurations
  • The HTTP endpoint is unauthenticated; use extra care when binding beyond loopback
  • Full local-search capabilities and some additional snippet features require a Pro plan
  • Search results and AI summaries depend on an external service and may require verification
  • Browser automation can be unpredictable on complex or sensitive sites; supervision is required
  • Credentials and payment info are stored in a vault but require user unlock flows
  • API keys are encrypted in Chrome storage, but clients may send page context to model providers
  • MCP server is a local process, posing local security risks
  • Capability catalog allows most non-denied origins but is gated by multiple checks
Supported clientsClaude Desktop, VS CodeClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex
Tools830