← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionFSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.Chrome DevTools MCPThe Chrome team's official MCP server exposing Chrome DevTools capabilities to AI assistants
FMRS66 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions14 / 2012 / 20
Maintenance15 / 2017 / 20
Documentation15 / 2017 / 20
Setup experience12 / 2017 / 20
Best for
  • 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
  • Frontend developers who want AI-assisted web debugging and performance analysis
  • Scenarios that need browser automation and performance diagnostics in the same tool
Not for
  • 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)
  • Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)
Required permissions
  • 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
  • Requires a local Chrome browser instance to run
  • navigate_page can visit any URL; type_text/fill_form and similar tools can enter arbitrary content into the page
Risks and side effects
  • 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
  • Browser automation tools can access and manipulate the content of open pages — use only in a trusted development/test environment
  • performance_start_trace and similar tracing tools continuously record browser activity — avoid leaving them running on pages containing sensitive information
Supported clientsClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, CodexClaude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Cline, Amp, Kiro, Antigravity
Tools3022