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.

DimensionNotebookLM MCP ServerDrive NotebookLM via a real Chrome browser, bringing citation-backed answers to your AI agents.FSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.
FMRS55 / 100 · C66 / 100 · C
Reliability6 / 2010 / 20
Security and permissions10 / 2014 / 20
Maintenance9 / 2015 / 20
Documentation17 / 2015 / 20
Setup experience13 / 2012 / 20
Best for
  • Power users needing reliable answers based on user-uploaded documents with reduced hallucinations.
  • Developers already using Claude Code, Cursor, or Codex who want to extend capabilities with NotebookLM.
  • Workflows that automate extensive document research or content generation.
  • 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
  • Users without a Google account or NotebookLM access.
  • Users who cannot run Chrome or headless servers without xvfb (WSL1 is not supported).
  • Those needing a lightweight, browserless solution (this server depends on a real Chrome).
  • 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 Google account login to access NotebookLM service.
  • Requires running Chrome/Chromium via Patchright, and may modify its profile files.
  • Can read/write local filesystem to store Chrome profiles, library data, and audio files.
  • May listen on local ports (default 3000 in HTTP mode) to serve MCP.
  • May make network requests to NotebookLM and Google services.
  • 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 trigger Google's anti-automation detection, potentially leading to account restrictions.
  • Chrome profile stores login credentials without encryption, posing credential leak risk.
  • Third-party source content may contain malicious instructions; AI marker and disclaimers mitigate but cannot eliminate risk.
  • Long-running sessions may accumulate browser sessions; monitor session timeouts and resource usage.
  • 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 Code, Cursor, Codex, Generic MCP client, HTTP-only clientsClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex
Tools1930