M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionComet MCPGive Claude Code a browser that thinks.FSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.
FMRS54 / 100 · D66 / 100 · C
Reliability8 / 2010 / 20
Security and permissions10 / 2014 / 20
Maintenance11 / 2015 / 20
Documentation12 / 2015 / 20
Setup experience13 / 2012 / 20
Best for
  • Developers needing deep web research and interactive browsing
  • Users who want to delegate browsing to a specialized AI
  • Tasks involving dynamic content or login walls
  • 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
  • Simple queries that don't require complex browser interaction
  • Users who don't install Comet browser
  • Users who need low-level control of the browser
  • 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
  • Auto-launch Comet browser
  • Communicate with browser via CDP
  • Read and write browser page content
  • Requires Node.js 18+ environment
  • 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
  • Browser automation may pose security risks; ensure trust in the source
  • Comet browser may collect usage data; consider privacy
  • Auto-launching browser may consume system resources
  • 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 DesktopClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex
Tools630