NotebookLM MCP Server drives a real browser profile to interact with Google NotebookLM., setup_auth opens an interactive login flow and persists cookies in a local Chrome profile for later reuse., Tools can add sources, ask questions, generate and download audio overviews, manage notebook library metadata, close sessions, reset sessions, and clean up stored data., cleanup_data and re_auth can wipe stored browser state or local server data, so review tool arguments before allowing destructive maintenance actions., Bind Streamable HTTP mode only on trusted networks and keep stdio as the default for local desktop clients.
Privacy notes
Google account cookies, NotebookLM notebook URLs, notebook metadata, source contents, questions, answers, citations, generated audio, browser session data, prompts, and tool outputs may be visible to the MCP client and model provider., The README notes there is no encrypted credential store; account separation is by Chrome profile directory., NotebookLM sources can contain private documents, internal research, customer material, legal drafts, meeting notes, and unreleased product plans., Review local profile and library storage before sharing machines, logs, screenshots, or exported artifacts.
Author
PleasePrompto
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access.
5 areas
SafetyLocal filesNotebookLM MCP Server drives a real browser profile to interact with Google NotebookLM.
SafetyLocal filessetup_auth opens an interactive login flow and persists cookies in a local Chrome profile for later reuse.
SafetyCredentials & tokensTools can add sources, ask questions, generate and download audio overviews, manage notebook library metadata, close sessions, reset sessions, and clean up stored data.
SafetyExecution & processescleanup_data and re_auth can wipe stored browser state or local server data, so review tool arguments before allowing destructive maintenance actions.
SafetyNetwork accessBind Streamable HTTP mode only on trusted networks and keep stdio as the default for local desktop clients.
PrivacyCredentials & tokensGoogle account cookies, NotebookLM notebook URLs, notebook metadata, source contents, questions, answers, citations, generated audio, browser session data, prompts, and tool outputs may be visible to the MCP client and model provider.
PrivacyCredentials & tokensThe README notes there is no encrypted credential store; account separation is by Chrome profile directory.
PrivacyGeneralNotebookLM sources can contain private documents, internal research, customer material, legal drafts, meeting notes, and unreleased product plans.
PrivacyLocal filesReview local profile and library storage before sharing machines, logs, screenshots, or exported artifacts.
Safety notes
NotebookLM MCP Server drives a real browser profile to interact with Google NotebookLM.
setup_auth opens an interactive login flow and persists cookies in a local Chrome profile for later reuse.
Tools can add sources, ask questions, generate and download audio overviews, manage notebook library metadata, close sessions, reset sessions, and clean up stored data.
cleanup_data and re_auth can wipe stored browser state or local server data, so review tool arguments before allowing destructive maintenance actions.
Bind Streamable HTTP mode only on trusted networks and keep stdio as the default for local desktop clients.
Privacy notes
Google account cookies, NotebookLM notebook URLs, notebook metadata, source contents, questions, answers, citations, generated audio, browser session data, prompts, and tool outputs may be visible to the MCP client and model provider.
The README notes there is no encrypted credential store; account separation is by Chrome profile directory.
NotebookLM sources can contain private documents, internal research, customer material, legal drafts, meeting notes, and unreleased product plans.
Review local profile and library storage before sharing machines, logs, screenshots, or exported artifacts.
Prerequisites
Node.js and npx available to the MCP client runtime.
Chrome or the bundled Patchright Chromium fallback available on the host.
Google account access for the NotebookLM notebooks you want to use.
One-time interactive authentication with setup_auth before headless reuse.
Local storage for the persisted Chrome profile, notebook library, sessions, and downloaded audio.
NotebookLM MCP Server connects MCP clients to Google NotebookLM through a real
Chrome profile. It can ask questions against notebooks, add sources, generate
and download audio overviews, manage a local notebook library, search notebooks,
inspect sessions, expose read-only library resources, and return citation-aware
answers.
The upstream README documents stdio and Streamable HTTP transports. The NPM
package exposes the notebooklm-mcp binary and the recommended local launch
path is npx notebooklm-mcp@latest.
These sources were reviewed on 2026-06-05. Prefer the live repository and
NPM registry metadata for current package version, command name, transport
support, browser requirements, authentication behavior, tools, and setup
guidance.
Features
Ask questions against a selected NotebookLM notebook.
Add web or text sources to notebooks.
Generate and download NotebookLM audio overviews.
Store and search a local notebook library.
Select active notebooks for repeated questions.
Manage browser sessions and reset chat history.
Run one-time Google authentication with persisted browser profile reuse.
Use trimmed tool profiles to reduce host-agent context usage.
Restart the MCP client, then run the authentication setup tool before asking
questions against NotebookLM notebooks.
Use Cases
Ask Claude grounded questions against a NotebookLM notebook.
Add a documentation source to a notebook for citation-backed Q&A.
Keep a local library of frequently used notebook share URLs.
Generate an audio overview for notebook sources.
Search and select notebooks before a research session.
Inspect citations returned from NotebookLM answers.
Safety and Privacy
NotebookLM MCP Server uses browser automation and persisted Google account
state. Review which account is authenticated, where browser profile data is
stored, and which notebooks are available before enabling it for an agent.
Destructive maintenance tools such as cleanup and re-authentication should stay
behind human approval.
NotebookLM notebooks can contain private documents and sensitive research.
Questions, answers, citations, source contents, local library metadata, browser
profile data, and generated audio may expose confidential context. Keep the
server local by default and avoid broad network exposure unless the deployment
is protected.
Duplicate Check
No PleasePrompto/notebooklm-mcp entry, notebooklm-mcp package entry, or
matching source URL was found in content/mcp.
Show that NotebookLM MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/notebooklm-mcp-server)
How it compares
NotebookLM MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
MCP server and CLI for searching Korean statutes, precedents, ordinances, treaties, interpretations, citation checks, amendment timelines, and legal scenario workflows through Korea's official law APIs.
MCP server for connecting Claude to AFFiNE Cloud or self-hosted AFFiNE workspaces, documents, databases, comments, collections, folders, tags, notifications, blobs, access tokens, semantic page composition, templates, edgeless canvas data, and workspace organization workflows over stdio or HTTP.
✓NotebookLM MCP Server drives a real browser profile to interact with Google NotebookLM.
setup_auth opens an interactive login flow and persists cookies in a local Chrome profile for later reuse.
Tools can add sources, ask questions, generate and download audio overviews, manage notebook library metadata, close sessions, reset sessions, and clean up stored data.
cleanup_data and re_auth can wipe stored browser state or local server data, so review tool arguments before allowing destructive maintenance actions.
Bind Streamable HTTP mode only on trusted networks and keep stdio as the default for local desktop clients.
✓Do not treat model output, tool summaries, scenario workflows, citation checks, or amendment comparisons as legal advice.
Verify legal conclusions against official Korean legal sources and a qualified professional before using them for compliance, litigation, contracts, immigration, employment, taxation, or public guidance.
Legal APIs can return stale, partial, unavailable, mistranslated, or context-dependent results; review dates, jurisdiction, document type, article numbers, and official text.
Chain tools and scenario tools can combine many sources into persuasive narratives; require citation review before relying on generated explanations.
Remote HTTP deployments must protect API keys, rate limits, and access to legal research workflows.
✓The full tool surface can create, update, publish, revoke, move, replace, and delete AFFiNE workspaces, documents, folders, collections, comments, database rows, blobs, surface elements, tags, and access tokens.
Start with AFFINE_TOOL_PROFILE=read_only or disable groups such as destructive, admin, blobs, users, access_tokens, docs.database, or write when the assistant only needs discovery or reading.
HTTP mode exposes MCP endpoints and must be protected with bearer or OAuth authentication, HTTPS, allowed origins, and deployment-level access controls.
AFFiNE Cloud requires API tokens for MCP usage; avoid trying to automate email/password login against Cloud deployments.
Cookie and password-based auth can grant broad account access and should be avoided for unattended or shared deployments.
✓AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API.
The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited.
Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns.
The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies.
Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.
Privacy notes
✓Google account cookies, NotebookLM notebook URLs, notebook metadata, source contents, questions, answers, citations, generated audio, browser session data, prompts, and tool outputs may be visible to the MCP client and model provider.
The README notes there is no encrypted credential store; account separation is by Chrome profile directory.
NotebookLM sources can contain private documents, internal research, customer material, legal drafts, meeting notes, and unreleased product plans.
Review local profile and library storage before sharing machines, logs, screenshots, or exported artifacts.
✓`LAW_OC` and any API-key delivery method must be treated as secret and kept out of repositories, shared prompts, logs, and screenshots.
Legal questions can reveal disputes, investigations, clients, employers, contracts, personal facts, regulated matters, or litigation strategy.
Queries, citations, law names, case numbers, document text, and generated legal analysis may be visible to the MCP client and model provider.
Avoid sending confidential client facts, privileged material, personal data, or non-public legal strategy through prompts or tool arguments.
✓Workspaces, document titles, document bodies, comments, tags, database schemas, database rows, edgeless canvas data, notifications, user profiles, access-token metadata, blobs, and exported markdown can be sent to the MCP client and model.
API tokens, cookies, passwords, bearer tokens, OAuth config, and saved config files should be treated as secrets and kept out of prompts, logs, screenshots, issues, and committed MCP config.
Generated or modified documents can persist in AFFiNE and may become visible to collaborators depending on workspace permissions and sharing state.
Blob upload, cleanup, export, and publish/revoke workflows can expose files, generated content, or collaboration state beyond the current prompt.
✓Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API.
Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material.
AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files.
Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.
Prerequisites
Node.js and npx available to the MCP client runtime.
Chrome or the bundled Patchright Chromium fallback available on the host.
Google account access for the NotebookLM notebooks you want to use.
One-time interactive authentication with setup_auth before headless reuse.
Node.js 20.19 or newer, matching the upstream package metadata.
Korea Law Open API key stored as `LAW_OC`.
Korean legal research context where Korea's statutes, precedents, ordinances, treaties, or interpretations are relevant.
Korean-language legal terminology familiarity or access to qualified review.
Node.js and npm for installing the affine-mcp-server package.
AFFiNE Cloud API token or approved self-hosted AFFiNE credentials.
AFFiNE base URL for the Cloud or self-hosted deployment.
Clear workspace scope and least-privilege tool profile before enabling write, admin, destructive, blob, or access-token tools.
Node.js and npx available to the MCP client runtime.
AgentQL API key from the AgentQL developer portal.
Approved list of public webpages or domains Claude may query.
Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.