Index of every page on this site: llms.txt
All skills
Run it yourself

Expert guide for the Gemini Notebook (formerly Google NotebookLM) CLI (`nlm`) and MCP server - interfaces for Gemini Notebook. Use this skill when users want to interact with Gemini Notebook programmatically, including: creating/managing notebooks, checking plan usage and quota windows, adding sources (URLs, YouTube, text, Google Drive), generating content (podcasts, reports, interactive reports, quizzes, flashcards, mind maps, slides, infographics, videos, data tables), conducting research, chatting with sources, or automating Gemini Notebook workflows. Triggers on mentions of "nlm", "notebooklm", "Gemini Notebook", "plan usage", "quota", "podcast generation", "audio overview", "interactive report", "lesson report", "refactor document", "critique draft", or any Gemini Notebook-related automation task.

  • 8 files
  • 190 KB
  • Updated last week
  • GitHub
Use this Skill: https://skilld.dev/gh/jacob-bd/gemini-notebook-mcp-cli/data

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesremote-mcp.md

≈866 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Remote MCP Deployment

Gemini Notebook (formerly Google NotebookLM) MCP supports Streamable HTTP, but it is designed primarily for local, single-user operation. It is not a secure, turnkey public connector.

Security Boundary

The MCP HTTP endpoint has no built-in authentication, authorization, or TLS. The server binds to loopback by default and refuses external binds unless NOTEBOOKLM_ALLOW_EXTERNAL_BIND=1 is set. That override only removes the bind guard; it does not secure the endpoint.

Never expose notebooklm-mcp directly to the public internet. If remote access is required:

  1. Keep the MCP process bound to 127.0.0.1.
  2. Put an authenticated HTTPS gateway in front of it.
  3. Restrict access to the owner of the active Gemini Notebook account.
  4. Protect the host because it stores Google session data.

Safe local HTTP startup:

notebooklm-mcp \
  --transport http \
  --host 127.0.0.1 \
  --port 8000 \
  --path /mcp

This exposes http://127.0.0.1:8000/mcp and a local health endpoint at http://127.0.0.1:8000/health. Monitors that probe the conventional /healthz path get the same response.

Authentication and Account Isolation

Remote operation involves two separate credentials:

  • The gateway must authenticate the MCP client.
  • nlm login must maintain the Google browser session used for Gemini Notebook.

The MCP server uses one process-wide Gemini Notebook profile. Every caller operates the same Google account, and nlm login switch <profile> changes the account for the whole server. An OAuth gateway controls access to the endpoint but does not create per-user Gemini Notebook isolation.

Google can require interactive sign-in again at any time. Persistent local browser profiles give the best recovery behavior. VPS and container deployments may require manual authentication maintenance, especially when storage is ephemeral or cookies are supplied only through environment variables. Remote and containerized servers without a desktop session or keyring daemon should keep profiles in file mode (nlm auth storage set file) or provide credentials via environment variables (NOTEBOOKLM_COOKIES).

Remote File Limitation

MCP file paths always refer to the filesystem of the machine running the server:

source_add(
    notebook_id="...",
    source_type="file",
    file_path="/path/on/server/document.pdf",
)

A browser or phone path is not uploaded automatically. Likewise, download_artifact(output_path=...) writes to the server host, inside that host's download directory (~/Downloads/gemini-notebook by default, or NOTEBOOKLM_DOWNLOAD_DIR), and paths outside it are refused. It does not return a secure browser download URL. Remote file upload and download require a separate, authenticated file-transfer layer.

Remote deployments are therefore best suited to URL, text, and Drive sources; research; queries; Studio creation/status; and metadata operations.

Deployment Guidance

  • For personal access from another device, prefer a remote-control workflow that leaves the MCP server, browser profile, and local files on the same trusted computer.
  • An advanced single-user connector can place an OAuth-capable HTTPS gateway in front of a loopback-only MCP process.
  • Public multi-user, organization-wide, VPS, container, reverse-proxy, and tunnel deployments are not supported turnkey configurations.

The full repository guide is docs/REMOTE_MCP.md.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 527ebc4. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated last week
version
0.16.5

README badge

README badge for jacob-bd/gemini-notebook-mcp-cli