Skip to main content
Glama
OneClickLM

OneClickLM

by CRtheHILLS

Hi! I'm CR šŸ‘‹

I built OneClickLM because I was tired of every NotebookLM MCP server breaking on me every few days.

After connecting NotebookLM to a 6-domain AI chatbot platform (BEYOND HUMAN), I hit literally every failure mode — expired tokens, Chrome crashes, concurrent query timeouts, you name it. So I built the tool I wished existed.

OneClickLM just works. Login once, forget about it forever.


Related MCP server: notebooklm-mcp-2026

šŸ’„ The Problem

Every NotebookLM MCP server on GitHub shares the same fatal flaw: they break within days.

Google silently rotates auth tokens, and no one handles it.

What happens

What you see

build_label expires (every 1-2 weeks)

šŸ”“ 400 Bad Request, zero explanation

CSRF token goes stale

šŸ”“ Queries silently fail

Chrome already running

šŸ”“ Login crashes with CDP conflict

Two queries at once

šŸ”“ Timeout cascade, server dies

Python + pipx + virtualenv

šŸ”“ 30 minutes just to install

Connection drops

šŸ”“ Queries hang forever

Sound familiar? Yeah, I went through all of this. So you don't have to.


āœ… The Solution

Feature

How it works

Auto-healing auth

Detects expired tokens → refreshes automatically → you never notice

Zero config

npx oneclicklm login once, then it just works. Forever.

No Chrome conflicts

Uses system Chrome for login, then pure HTTP. No CDP, no conflicts.

Smart queue

Serializes concurrent calls. No timeouts, no crashes.

6 powerful tools

List, query, create notebooks + add sources. Everything you need.

TypeScript native

No Python, no virtualenv, no pipx. Just Node.js.


šŸš€ Quick Start

Step 1: Login (one time only)

npx oneclicklm login

A browser opens → sign in with Google → done. Your cookies are saved locally (~/.oneclicklm/).

Step 2: Add to your MCP client

{
  "mcpServers": {
    "notebooklm": {
      "command": "npx",
      "args": ["oneclicklm"]
    }
  }
}

Step 3: Start talking to your notebooks!

"List my NotebookLM notebooks"
"What are the key findings in my Research notebook?"
"Create a new notebook called 'Project Alpha'"
"Add this URL to my notebook: https://example.com/paper.pdf"

That's it. No API keys, no profiles, no metadata.json, no build_label hunting.


šŸ›  Available Tools

Tool

What it does

Example prompt

notebook_list

List all your notebooks

"Show me my NotebookLM notebooks"

notebook_get

Get notebook details + sources

"What sources are in my Research notebook?"

notebook_query

Ask questions, get cited answers

"What does my notebook say about X?"

notebook_create

Create a new notebook

"Create a notebook called 'Q1 Report'"

source_add

Add URL, YouTube, or text sources

"Add this article to my notebook"

source_list

List all sources + their status

"Show sources in my Project notebook"

Pro tip: notebook_query uses the same AI (Gemini) as the NotebookLM web app — your answers are grounded in your actual sources with zero hallucination.


šŸ’» IDE Setup

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "notebooklm": {
      "command": "npx",
      "args": ["oneclicklm"]
    }
  }
}
claude mcp add notebooklm -- npx oneclicklm

Add to .vscode/mcp.json:

{
  "servers": {
    "notebooklm": {
      "command": "npx",
      "args": ["oneclicklm"]
    }
  }
}

Add to ~/.windsurf/mcp.json:

{
  "mcpServers": {
    "notebooklm": {
      "command": "npx",
      "args": ["oneclicklm"]
    }
  }
}

šŸ” How OneClickLM Compares

Feature

OneClickLM

notebooklm-mcp (Python)

notebooklm-mcp-cli

Auto token refresh

āœ…

āŒ

āŒ

Auto build_label update

āœ…

āŒ

āŒ

Auto-reconnect on failure

āœ…

āŒ

āŒ

Request queue (no crashes)

āœ…

āŒ

āŒ

Zero-config install

āœ… npx

āŒ pipx + profiles

āŒ pipx + profiles

Language

TypeScript

Python

Python

Chrome conflicts

None

Common

Common

Human-readable errors

āœ…

āŒ

āŒ

Create notebooks via MCP

āœ…

āŒ

āœ…

Add sources via MCP

āœ…

āŒ

āœ…


āš™ļø Configuration

OneClickLM works with zero configuration. But if you need it:

# Custom config directory
ONECLICKLM_DIR=~/.my-config npx oneclicklm

# Debug logging (see what's happening under the hood)
ONECLICKLM_LOG=debug npx oneclicklm

# Custom request timeout (default: 30s, queries may need longer)
ONECLICKLM_TIMEOUT=60000 npx oneclicklm

# Custom Chrome path
CHROME_PATH=/path/to/chrome npx oneclicklm login

Config is stored in ~/.oneclicklm/:

~/.oneclicklm/
ā”œā”€ā”€ cookies.json    # Google auth cookies (auto-managed)
└── tokens.json     # CSRF + session + build_label (auto-refreshed)

🧠 How It Works (for the curious)

OneClickLM speaks the same language as the NotebookLM web app — Google's internal batchexecute RPC protocol.

Here's what happens when you ask a question:

You: "What are the key findings?"
 ↓
MCP Client (Cursor/Claude/VS Code) sends tool call
 ↓
OneClickLM checks tokens → auto-refreshes if stale
 ↓
Fetches source IDs from notebook (RPC: rLM1Ne)
 ↓
Sends query via streaming endpoint (GenerateFreeFormStreamed)
 ↓
Parses streaming response → extracts answer
 ↓
Returns grounded, cited answer to your AI

The magic is in the auto-healing auth:

  1. On startup: loads saved cookies + cached tokens

  2. If tokens expired (>1 hour): fetches NotebookLM page → extracts fresh SNlM0e (CSRF) + FdrFJe (session) + build_label

  3. If cookies expired (~30 days): prompts for re-login

  4. If API returns 400/401: auto-refreshes tokens and retries once

  5. All requests serialized through a queue → no concurrent crash

NOTE

OneClickLM uses Google's internal web protocol, not an official API. This means it works with your existing Google account — no API keys, no billing, no quotas. Google AI Pro subscribers get full NotebookLM access.


šŸ”§ Troubleshooting

Make sure Chrome/Chromium is installed. OneClickLM detects it automatically on macOS, Windows, and Linux.

# If using a non-standard Chrome location:
CHROME_PATH=/path/to/chrome npx oneclicklm login

OneClickLM auto-refreshes tokens, but if it persists:

# Force token refresh
npx oneclicklm refresh

# Nuclear option: re-login
npx oneclicklm login

This is normal. NotebookLM processes your query against all uploaded sources in real-time (this is the Gemini model working). The NotebookLM web app has similar response times. For faster results, use notebooks with fewer sources.

npx oneclicklm status

This verifies cookies, extracts fresh tokens, and tells you if anything is wrong.


šŸ¤ Contributing

Contributions welcome! Bug reports, feature requests, and PRs are all appreciated.

git clone https://github.com/CRtheHILLS/OneClickLM.git
cd OneClickLM
npm install
npm run build
node dist/src/index.js  # Run locally

⭐ Star History

If OneClickLM saved you from NotebookLM auth hell, consider starring the repo!


License

MIT Ā© CRtheHILLS


Available Tools

6 tools
notebook_createA

Create a new empty NotebookLM notebook. After creating, use source_add to add content.

Inputs: title (required).

notebook_getA

Get detailed information about a specific notebook, including all its sources and their status.

Inputs: notebook_id (required).

notebook_listA

List all your NotebookLM notebooks. Returns notebook IDs, titles, and source counts. Use this first to discover available notebooks.

Inputs: no named parameters.

notebook_queryA

Ask a natural language question to a NotebookLM notebook. The AI will analyze all sources in the notebook and return a grounded, cited answer. This is the main tool for getting information from your notebooks.

Inputs: query (required), notebook_id (required).

source_addA

Add a source to a NotebookLM notebook. Supports URLs (web pages, articles), YouTube videos, and plain text content. The source will be processed and made available for queries.

Inputs: type (required), notebook_id (required), url, title, +1 more.

source_listA

List all sources in a NotebookLM notebook, including their titles and processing status (ready, processing, error).

Inputs: notebook_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing, getting, querying, creating notebooks, and adding/listening to sources. No overlapping functionality.

    Naming Consistency5/5

    All tool names follow a consistent noun_verb pattern (e.g., notebook_list, source_add), with snake_case throughout.

    Tool Count5/5

    6 tools is well-scoped for managing NotebookLM notebooks, covering creation, querying, and source management without being excessive or insufficient.

    Completeness4/5

    Covers core workflows well but lacks delete or update operations for notebooks and sources, which may be needed for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers