Gemini Notebook (formerly Google NotebookLM) CLI & MCP Server

Programmatic access to Gemini Notebook — via command-line interface (CLI) or Model Context Protocol (MCP) server.

> Note: Personal/consumer accounts are tested regularly. Gemini Notebook Enterprise support is experimental. The documented `notebook.cloud.google.com` host has been live-verified with a project-qualified `global` deployment; other Enterprise host variants may require additional validation.

> ☕ **If you find notebooklm-mcp-cli useful, consider buying me a coffee.**

> It's free and built in my spare time — but testing every Gemini Notebook feature takes real time and resources. A coffee helps me cover it and keep shipping. Thank you! 🙏

>

>

📺 Watch the Demos

Latest

MCP Demos

CLI Demos

Two Ways to Use

🖥️ Command-Line Interface (CLI)

Use `nlm` directly in your terminal for scripting, automation, or interactive use:

nlm notebook list                              # List all notebooks
nlm notebook create "Research Project"         # Create a notebook
nlm source add  --url "https://..."  # Add sources
nlm audio create  --confirm          # Generate podcast
nlm download audio  --id     # Download audio file
nlm download all  -d ./exports       # Download every artifact
nlm share public                     # Enable public link

Run `nlm --ai` for comprehensive AI-assistant documentation.

🤖 MCP Server (for AI Agents)

Connect AI assistants (Claude, Gemini, Cursor, etc.) to Gemini Notebook:

# Automatic setup — picks the right config for each tool
nlm setup add claude-code
nlm setup add claude-desktop
nlm setup add gemini
nlm setup add github-copilot
nlm setup add cursor
nlm setup add cline
nlm setup add antigravity

# Generate JSON config for any other tool
nlm setup add json

Then use natural language: _"Create a notebook about quantum computing and generate a podcast"_

Features

📚 More Documentation:

• **Getting Started** — Install, login, agent setup, and migration from another Gemini Notebook MCP
• **CLI Guide** — Complete command reference
• **MCP Guide** — All 43 MCP tools with examples
• **Authentication** — Setup and troubleshooting
• **Remote MCP** — Web/mobile connector feasibility, security, and authentication limitations
• **API Reference** — Internal API docs for contributors

Important Disclaimer

This MCP and CLI use internal APIs that:

• Are undocumented and may change without notice
• Require cookie extraction from your browser (I have a tool for that!)

Use at your own risk for personal/experimental purposes.

Installation

> 🆕 Claude Desktop users: Download the extension (`.mcpb` file) → double-click → done! One-click install, no config needed.

Install from PyPI. This single package includes both the CLI and MCP server:

Using uv (Recommended)

uv tool install notebooklm-mcp-cli

Using uvx (Run Without Install)

uvx --from notebooklm-mcp-cli nlm --help
uvx --from notebooklm-mcp-cli notebooklm-mcp

Using pip

pip install notebooklm-mcp-cli

Using pipx

pipx install notebooklm-mcp-cli

After installation, you get:

• `nlm` — Command-line interface
• `notebooklm-mcp` — Gemini Notebook MCP server for AI assistants

Alternative: Install from Source

# Clone the repository
git clone https://github.com/jacob-bd/gemini-notebook-mcp-cli.git
cd notebooklm-mcp

# Install with uv
uv tool install .

Upgrading

# Using uv
uv tool upgrade notebooklm-mcp-cli

# Using pip
pip install --upgrade notebooklm-mcp-cli

# Using pipx
pipx upgrade notebooklm-mcp-cli

After upgrading, restart your AI tool to reconnect to the updated MCP server:

• Claude Code: Restart the application, or use `/mcp` to reconnect
• Cursor: Restart the application
• Gemini CLI: Restart the CLI session

Upgrading from Legacy Versions

If you previously installed the separate CLI and MCP packages, you need to migrate to the unified package.

Step 1: Check What You Have Installed

uv tool list | grep notebooklm

Legacy packages to remove:

Step 2: Uninstall Legacy Packages

# Remove old CLI package (if installed)
uv tool uninstall notebooklm-cli

# Remove old MCP package (if installed)
uv tool uninstall notebooklm-mcp-server

Step 3: Reinstall the Unified Package

After removing legacy packages, reinstall to fix symlinks:

uv tool install --force notebooklm-mcp-cli

> Why `--force`? When multiple packages provide the same executable, `uv` can leave broken symlinks after uninstalling. The `--force` flag ensures clean symlinks.

Step 4: Verify Installation

uv tool list | grep notebooklm

You should see only:

notebooklm-mcp-cli v0.2.0
- nlm
- notebooklm-mcp

Step 5: Re-authenticate

Your existing cookies should still work, but if you encounter auth issues:

nlm login

> Note: The configured MCP server name is now `gemini-notebook-mcp`. The executable remains `notebooklm-mcp` for compatibility with existing installations.

Getting Started

If you are setting up the tool for the first time — or migrating from a

browser-based Gemini Notebook MCP — see the

Getting Started Guide. It covers install,

login, agent registration, and a step-by-step migration path that avoids

the "two Gemini Notebook servers registered" trap.

Uninstalling

To completely remove the MCP:

# Using uv
uv tool uninstall notebooklm-mcp-cli

# Using pip
pip uninstall notebooklm-mcp-cli

# Using pipx
pipx uninstall notebooklm-mcp-cli

# Remove cached auth tokens and data (optional)
rm -rf ~/.notebooklm-mcp-cli

Also remove from your AI tools:

nlm setup remove claude-code
nlm setup remove cursor
# ... or any configured tool

Authentication

Before using the CLI or MCP, you need to authenticate with Gemini Notebook:

CLI Authentication (Recommended)

# Auto mode: launches your browser, you log in, cookies extracted automatically
nlm login

# Check if already authenticated
nlm login --check

# Use a named profile (for multiple Google accounts)
nlm login --profile work
nlm login --profile personal

# Manual mode: import cookies from a file
nlm login --manual --file cookies.txt

# External CDP provider (e.g., OpenClaw-managed browser)
nlm login --provider openclaw --cdp-url http://127.0.0.1:18800

Profile management:

nlm login --check                    # Show current auth status
nlm login switch            # Switch the default profile
nlm login profile list               # List all profiles with email addresses
nlm login profile delete    # Delete a profile
nlm login profile rename   # Rename a profile

Enterprise Authentication (Gemini Notebook Enterprise)

For organizations using Gemini Notebook Enterprise via Google Cloud, ask your Enterprise administrator for the project ID or number, the deployment location/multi-region, and confirmation that your account has access. The current documented host is `notebook.cloud.google.com`; older deployments may use `notebooklm.cloud.google.com` or `vertexaisearch.cloud.google.com`.

1. Set Base URL, GCP Project ID & Location:

export NOTEBOOKLM_BASE_URL="https://notebook.cloud.google.com"
   # Required: your GCP project ID or project number from your administrator
   export NOTEBOOKLM_PROJECT_ID="your-gcp-project-id-or-number"
   # Optional: GCP location/multi-region from your administrator: global (default), us, or eu
   export NOTEBOOKLM_LOCATION="global"

2. Save an Enterprise Auth Profile:

This opens the configured Enterprise URL in an isolated browser profile. Sign in with your organization account:

nlm login --profile enterprise
   nlm login switch enterprise

You can switch back to a personal profile at any time:

unset NOTEBOOKLM_BASE_URL NOTEBOOKLM_PROJECT_ID NOTEBOOKLM_LOCATION
   nlm login switch personal

3. Configure MCP Server with Enterprise Environment Variables:

When adding the MCP server to AI assistants (Claude, Cursor, etc.), pass `NOTEBOOKLM_BASE_URL`, `NOTEBOOKLM_PROJECT_ID`, and optionally `NOTEBOOKLM_LOCATION`:

{
     "mcpServers": {
       "gemini-notebook-mcp": {
         "command": "notebooklm-mcp",
         "env": {
           "NOTEBOOKLM_BASE_URL": "https://notebook.cloud.google.com",
           "NOTEBOOKLM_PROJECT_ID": "your-gcp-project-id-or-number",
           "NOTEBOOKLM_LOCATION": "global"
         }
       }
     }
   }

Each profile gets its own isolated browser session, so you can be logged into multiple Google accounts simultaneously. Enterprise environment variables apply to the current process, so keep them in an Enterprise-only shell or MCP configuration when you also use a personal account.

Standalone Auth Tool

If you only need the MCP server (not the CLI):

nlm login              # Auto mode (launches browser)
nlm login --manual     # Manual file mode

How it works: Auto mode launches a dedicated browser profile (supports Chrome, Arc, Dia, Comet, Brave, Edge, Chromium, Firefox, and more), you log in to Google, and cookies are extracted automatically. Your login persists for future auth refreshes.

Prefer a specific browser? Set it with `nlm config set auth.browser chromium` (or `comet`, `dia`, `brave`, `arc`, `edge`, `chrome`, `firefox`, etc.). Falls back to auto-detection if the preferred named browser is not found. For any other Chromium-compatible browser, set its executable with `nlm config set auth.browser_path /path/to/browser` or `NLM_BROWSER_PATH`; an invalid explicit path fails closed instead of launching a different browser. When Chromium/CDP is unavailable, `auto` can fall back to Firefox.

For detailed instructions and troubleshooting, see **docs/AUTHENTICATION.md**.

MCP Configuration

> ⚠️ Context Window Warning: This MCP provides 43 tools. Disable it when not using Gemini Notebook to preserve context. In Claude Code: `@gemini-notebook-mcp` to toggle. To keep it on but expose only a subset, see Selective tool exposure.

Automatic Setup (Recommended)

Use `nlm setup` to automatically configure the MCP server for your AI tools — no manual JSON editing required:

# Add to any supported tool
nlm setup add claude-code
nlm setup add claude-desktop
nlm setup add claude-desktop --profile 3p  # Relay AI / Claude 3P
nlm setup add gemini
nlm setup add github-copilot
nlm setup add cursor
nlm setup add windsurf

# Generate JSON config for any other tool
nlm setup add json

# Check which tools are configured
nlm setup list

# Diagnose installation & auth issues
nlm doctor

Claude Desktop setup only writes to profiles that are detected as present. If

both regular and Relay AI/3P profiles exist, the CLI asks whether to configure

regular, 3P, or both. For scripts, use `--profile regular|3p|both`. If no

Claude Desktop profile is detected, nothing is created or changed.

Removal uses the same profile selection, for example

`nlm setup remove claude-desktop --profile regular`.

Removal only offers detected profiles containing this MCP or a recognized

legacy entry; unrelated MCP servers are left untouched.

Before adding or removing the MCP, fully quit the selected Claude Desktop

profile. The CLI detects running regular and Relay AI/3P instances and refuses

to write while they are open, because Claude may rewrite the config and discard

the change. Reopen Claude Desktop after setup completes.

Install AI Skills (Optional)

Install the Gemini Notebook expert guide for your AI assistant to help it use the tools effectively. Supported for Cline, Antigravity, OpenClaw, Codex, OpenCode, Claude Code, and Gemini CLI.

# Install skill files
nlm skill install cline
nlm skill install openclaw
nlm skill install codex
nlm skill install antigravity

# Update skills
nlm skill update

User-level skill installation requires the target tool to be detected first;

the CLI will not create a missing tool directory or install anyway. Use

`--level project` when you intentionally want a project-local skill.

Remove from a tool

nlm setup remove claude-code

Using uvx (No Install Required)

If you don't want to install the package, you can use `uvx` to run on-the-fly:

# Run CLI commands directly
uvx --from notebooklm-mcp-cli nlm setup add cursor
uvx --from notebooklm-mcp-cli nlm login

For tools that use JSON config, point them to uvx:

{
  "mcpServers": {
    "gemini-notebook-mcp": {
      "command": "uvx",
      "args": ["--from", "notebooklm-mcp-cli", "notebooklm-mcp"]
    }
  }
}

Manual Setup (if you prefer)

> Tip: Run `nlm setup add json` for an interactive wizard that generates the right JSON snippet for your tool.

Claude Code / Gemini CLI support adding MCP servers via their own CLI:

claude mcp add --scope user gemini-notebook-mcp notebooklm-mcp
gemini mcp add --scope user gemini-notebook-mcp notebooklm-mcp

Cursor / Windsurf resolve commands from your `PATH`, so the command name is enough:

{
  "mcpServers": {
    "gemini-notebook-mcp": {
      "command": "notebooklm-mcp"
    }
  }
}

GitHub Copilot (VS Code workspace) uses `.vscode/mcp.json` with a top-level `servers` key:

{
  "servers": {
    "gemini-notebook-mcp": {
      "command": "notebooklm-mcp",
      "args": []
    }
  }
}

Claude Desktop may not resolve `PATH` — use the full path to the binary:

{
  "mcpServers": {
    "gemini-notebook-mcp": {
      "command": "/full/path/to/notebooklm-mcp"
    }
  }
}

Find your path with: `which notebooklm-mcp`

📚 Full configuration details: MCP Guide — Server options, environment variables, HTTP transport, and context window management. For Claude web/mobile and public deployment, read Remote MCP Deployment first.

What You Can Do

Simply chat with your AI tool (Claude Code, Cursor, Gemini CLI) using natural language. Here are some examples:

Research & Discovery

• "List all my Gemini Notebook notebooks"
• "Create a new notebook called 'AI Strategy Research'"
• "Start web research on 'enterprise AI ROI metrics' and show me what sources it finds"
• "Do a deep research on 'cloud marketplace trends' and import the top 10 sources"
• "Search my Google Drive for documents about 'product roadmap' and create a notebook"

Adding Content

• "Add this URL to my notebook: https://example.com/article"
• "Add this YouTube video about Kubernetes to the notebook"
• "Add my meeting notes as a text source to this notebook"
• "Import this Google Doc into my research notebook"

AI-Powered Analysis

• "What are the key findings in this notebook?"
• "Summarize the main arguments across all these sources"
• "What does this source say about security best practices?"
• "Get an AI summary of what this notebook is about"
• "Configure the chat to use a learning guide style with longer responses"

_(All queries sent from CLI or MCP automatically persist in your Gemini Notebook web UI chat history!)_

Content Generation

• "Create an audio podcast overview of this notebook in deep dive format"
• "Generate a video explainer with classic visual style"
• "Make a short vertical video overview of the key idea"
• "Make a briefing doc from these sources"
• "Create flashcards for studying, medium difficulty"
• "Generate an infographic in landscape orientation with professional style"
• "Build a mind map from my research sources"
• "Create a slide deck presentation from this notebook"

Smart Management

• "Check which Google Drive sources are out of date and sync them"
• "Show me all the sources in this notebook with their freshness status"
• "Delete this source from the notebook"
• "Check the status of my audio overview generation"
• "Check this specific artifact without listing every Studio item"
• "List only the generated videos in this notebook"

Sharing & Collaboration

• "Show me the sharing settings for this notebook"
• "Make this notebook public so anyone with the link can view it"
• "Disable public access to this notebook"
• "Invite user@example.com as an editor to this notebook"
• "Add a viewer to my research notebook"

Pro tip: After creating studio content (audio, video, reports, etc.), poll the status to get download URLs when generation completes.

Authentication Lifecycle

v0.1.9+: The server now automatically handles token expiration:

1. Refreshes CSRF tokens immediately when expired

2. Reloads cookies from disk if updated externally

3. Runs headless browser auth if profile has saved login

You can also call `refresh_auth()` to explicitly reload tokens.

If automatic refresh fails (Google login fully expired), run `nlm login` again.

For suspected browser-bound auth replay failures, run `nlm doctor auth-replay`.

If the `cdp_in_page` probe succeeds while normal replay fails, see

Experimental browser-backed RPC transport.

Troubleshooting

`uv tool upgrade` Not Installing Latest Version

Symptoms:

• Running `uv tool upgrade notebooklm-mcp-cli` installs an older version (e.g., 0.1.5 instead of 0.1.9)
• `uv cache clean` doesn't fix the issue

Why this happens: `uv tool upgrade` respects version constraints from your original installation. If you initially installed an older version or with a constraint, `upgrade` stays within those bounds by design.

Fix — Force reinstall:

uv tool install --force notebooklm-mcp-cli

This bypasses any cached constraints and installs the absolute latest version from PyPI.

Verify:

uv tool list | grep notebooklm
# Should show: notebooklm-mcp-cli v0.1.9 (or latest)

Limitations

• Rate limits: Free tier has ~50 queries/day
• No official support: API may change without notice
• Cookie expiration: Need to re-extract cookies every few weeks

Contributing

See CLAUDE.md for detailed API documentation and how to add new features.

Vibe Coding Alert

Full transparency: this project was built by a non-developer using AI coding assistants. If you're an experienced Python developer, you might look at this codebase and wince. That's okay.

The goal here was to scratch an itch - programmatic access to Gemini Notebook - and learn along the way. The code works, but it's likely missing patterns, optimizations, or elegance that only years of experience can provide.

This is where you come in. If you see something that makes you cringe, please consider contributing rather than just closing the tab. This is open source specifically because human expertise is irreplaceable. Whether it's refactoring, better error handling, type hints, or architectural guidance - PRs and issues are welcome.

Think of it as a chance to mentor an AI-assisted developer through code review. We all benefit when experienced developers share their knowledge.

Credits

Special thanks to:

• Le Anh Tuan (@latuannetnam) for contributing the HTTP transport, debug logging system, and performance optimizations.
• David Szabo-Pele (@davidszp) for the `source_get_content` tool and Linux auth fixes.
• saitrogen (@saitrogen) for the research polling query fallback fix.
• devnull03 (@devnull03) for multi-browser CDP authentication support (Arc, Brave, Edge, Chromium, Vivaldi, Opera).
• VooDisss (@VooDisss) for multi-browser authentication improvements.
• codepiano (@codepiano) for the configurable DevTools timeout for the auth CLI.
• Tony Hansmann (@997unix) for contributing the `nlm setup` and `nlm doctor` commands and CLI Guide documentation.
• Fabiana Furtado (@fabianafurtadoff) for batch operations, cross-notebook query, pipelines, and smart select/tagging (PR #90).
• Amy-Ra-lph (@Amy-Ra-lph) for security hardening: TOCTOU-safe credential storage, sensitive cookie redaction from debug logs, and pinning all CI actions to full commit SHAs (PRs #205–207).
• Kyle Brodeur (@kylebrodeur) for WSL2 authentication support with Windows Chrome integration (PR #138).
• Robiton (@Robiton) for enterprise Gemini Notebook support via configurable base URL (PR #114).
• pjeby (@pjeby) for connection pooling and fast startup improvements (PR #54).
• beausea (@beausea) for making the interface language configurable via the `NOTEBOOKLM_HL` environment variable (PR #59).
• JumpLao (@JumpLao) for extended audio, video, and image format support (PR #82).
• cbruyndoncx (@cbruyndoncx) for including `cited_text` passages in query output (PR #81).
• zxyasfas (@zxyasfas) for cited-only research import (PR #188).
• Serdar Akın (@SERDAR-AKIN) for the multi-probe `AuthHealthChecker` that fixes false `"stale"` reports for semi-stale cookies (PR #219).

Star History

License

MIT License