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.Playwright MCPMicrosoft's official Playwright-based browser automation MCP server
FMRS55 / 100 · C78 / 100 · B
Reliability6 / 2013 / 20
Security and permissions10 / 2012 / 20
Maintenance9 / 2018 / 20
Documentation17 / 2018 / 20
Setup experience13 / 2017 / 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.
  • Scenarios where an AI assistant needs to actually drive a browser to complete a task
  • Web automation testing and end-to-end verification
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).
  • Simple static-text scraping (a lightweight scraper is a better fit)
  • Environments sensitive to browser resource usage that can't run a full browser engine
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 and running a browser engine (Chromium/Firefox/WebKit) locally or on a server
  • browser_navigate can visit any URL; browser_evaluate can run arbitrary JavaScript in the page context
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_evaluate executing arbitrary scripts carries risk if a malicious page is visited — restrict to trusted sites or an isolated environment
  • Long-running browser instances consume significant memory and CPU
Supported clientsClaude Code, Cursor, Codex, Generic MCP client, HTTP-only clientsClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Cline, Amp, Kiro, LM Studio, Antigravity, Goose
Tools1910