Skip to main content
Glama
README.md
# notebooklm-skill

> Source-grounded NotebookLM automation for terminals and AI agents.

[![CI](https://github.com/claude-world/notebooklm-skill/actions/workflows/ci.yml/badge.svg)](https://github.com/claude-world/notebooklm-skill/actions/workflows/ci.yml)
[![PyPI](https://img.shields.io/pypi/v/notebooklm-skill)](https://pypi.org/project/notebooklm-skill/)
[![Python](https://img.shields.io/pypi/pyversions/notebooklm-skill)](https://pypi.org/project/notebooklm-skill/)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

[繁體中文](README.zh-TW.md)

`notebooklm-skill` gives humans and MCP clients one consistent interface for Google
NotebookLM. It creates notebooks from URLs, raw text, and local files; asks grounded
questions with citation metadata; completes fast or deep web research; and generates
or downloads NotebookLM artifacts.

The project is built on `notebooklm-py` 0.8.x and FastMCP 4 (MCP Python SDK 2.x),
and includes:

- a JSON-first core CLI;
- five end-to-end research pipelines;
- a 13-tool FastMCP server;
- profile-aware authentication and Skill installers;
- one shared compatibility layer, so CLI, pipelines, and MCP use the same behavior.

> This is an unofficial integration with NotebookLM's web API. Google can change the
> service, availability, quotas, or artifact behavior without notice.

## Requirements

- Python 3.10 or newer (CI covers 3.10 through 3.15)
- a Google account with access to NotebookLM
- Chromium for the one-time browser login (installed by `./install.sh`), or a local
  Google Chrome or Microsoft Edge
- optional: the `trend-pulse` command for trend workflows, and `ffmpeg` plus Poppler
  for `scripts/make_video.sh`

## Quick start

### Isolated source install

The installer creates a dedicated virtual environment, installs Chromium, links five
commands into `~/.local/bin`, and installs the Claude Code Skill using the standard
directory layout.

```bash
git clone https://github.com/claude-world/notebooklm-skill.git
cd notebooklm-skill
./install.sh

notebooklm-auth setup
notebooklm-skill list
```

Ensure `~/.local/bin` is on `PATH`.

### PyPI or uvx

```bash
# Persistent virtual environment
python3 -m venv .venv
source .venv/bin/activate
python -m pip install notebooklm-skill
python -m playwright install chromium
notebooklm-auth setup

# Or run without a persistent install
uvx --from notebooklm-skill notebooklm-auth setup
uvx --from notebooklm-skill notebooklm-skill list
```

Direct upstream login is also available:

```bash
uvx --from notebooklm-py notebooklm login
```

Sessions are profile-aware. Select one with `--profile NAME` before a CLI
subcommand, or set `NOTEBOOKLM_PROFILE`.

To use the locally installed Google Chrome instead of bundled Chromium:

```bash
notebooklm-auth setup --browser chrome --fresh
```

## Core CLI

All successful commands print structured JSON to stdout. Diagnostics go to stderr;
authentication errors return exit code 4 and argument errors return exit code 2.

```bash
# Mixed-source ingestion with truthful per-source outcomes
notebooklm-skill create \
  --title "Research" \
  --sources https://example.com/article \
  --files ./paper.pdf \
  --text-sources "Interview notes" \
  --strict

notebooklm-skill ask \
  --notebook "Research" \
  --query "Which conclusions have the strongest evidence?"

notebooklm-skill research \
  --notebook "Research" \
  --query "Recent independent evaluations" \
  --mode deep --max-sources 10

notebooklm-skill generate \
  --notebook "Research" \
  --type slides --lang zh-TW \
  --output ./output/deck.pptx --output-format pptx

notebooklm-skill list-artifacts --notebook "Research" --type slides
```

Commands resolve an exact ID, unique title, or unique title substring. Use IDs for
repeatable automation. Deletes require `--yes`; downloads refuse existing files or
symlinks unless an explicit safe overwrite is requested with `--force`.

### Artifact types

| Type | Default download | Notes |
|---|---:|---|
| `audio` | M4A | deep-dive, brief, critique, or debate |
| `video` | MP4 | explainer, brief, or vertical short; multiple visual styles |
| `cinematic` | MP4 | cinematic video workflow |
| `slides` | PDF | PDF or PPTX |
| `report` | Markdown | briefing, study guide, blog, or custom |
| `study-guide` | Markdown | report shortcut |
| `quiz` | JSON | JSON, Markdown, or HTML; fewer, standard, or more questions |
| `flashcards` | JSON | JSON, Markdown, or HTML; fewer, standard, or more cards |
| `mind-map` | JSON | immediate generation result |
| `infographic` | PNG | orientation, detail, and style options |
| `data-table` | CSV | structured extraction |

Use `notebooklm-skill generate --help` for the live option matrix. Long-running
generations support `--no-wait`, and later downloads can select `--artifact-id`.

## Pipelines

```bash
notebooklm-pipeline research-to-article \
  --sources https://example.com/a https://example.com/b \
  --title "Evidence review" --audience "engineers"

notebooklm-pipeline research-to-social \
  --files ./brief.pdf --platform linkedin --variants 3

notebooklm-pipeline batch-digest \
  --rss https://example.com/feed.xml --max-entries 20 --qa-count 5

notebooklm-pipeline generate-all \
  --files ./paper.pdf --types audio slides report mind-map \
  --output-dir ./output --artifact-concurrency 2
```

`trend-to-content` requires the optional `trend-pulse` command. Pipelines return
drafts and local artifacts; they do not publish to social platforms or remote CMSs.

## MCP server

The default stdio transport is suitable for Claude Code, Cursor, and other MCP
clients:

```json
{
  "mcpServers": {
    "notebooklm": {
      "command": "uvx",
      "args": ["--from", "notebooklm-skill", "notebooklm-mcp"]
    }
  }
}
```

The 13 tools cover notebook CRUD, mixed sources, grounded chat, summaries, artifact
generation/list/download, full research lifecycles, research pipelines, and trend
research. Notebook deletion requires `confirm=true`.

Optional HTTP mode is deliberately loopback-only:

```bash
notebooklm-mcp --http --host 127.0.0.1 --port 8765
```

Do not expose it directly to a network. See [SECURITY.md](SECURITY.md).

## Additional commands

| Command | Purpose |
|---|---|
| `notebooklm-auth` | Setup, verify, or clear a selected auth profile |
| `notebooklm-install-skill` | Install `SKILL.md` for a user or project, with safe backups |

```bash
notebooklm-install-skill --scope project
notebooklm-auth --profile work verify
```

## Development

```bash
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -e '.[dev]'
ruff check .
ruff format --check .
mypy scripts mcp_server
pytest --cov --cov-report=term-missing
python -m build
twine check dist/*
```

More detail: [setup guide](docs/SETUP.md), [Skill instructions](SKILL.md),
[API compatibility notes](references/api_surface.md), and [changelog](CHANGELOG.md).

## License

[MIT](LICENSE)

TDQS

A3.6/5.0

Scored across 38 tools

Disambiguation3/5

Most tools target distinct resources, but the source-add family is genuinely confusing: source_add already handles file/drive/url/text/youtube, yet separate source_add_drive_file and source_add_play_book exist with overlapping surface. The chat pair (chat_ask blocking vs chat_start detached) and studio tool cluster are heavily documented to compensate, but an agent still has to read carefully to pick correctly.

Naming Consistency4/5

Consistent snake_case with a clear domain-prefix scheme (notebook_*, source_*, chat_*, studio_*, research_*, share_*). Minor deviations: verbs flip between noun_verb (notebook_create, chat_start) and verb_noun (share_set_access, share_remove_user), and outliers like await_upload and suggest_prompts lack a domain prefix.

Tool Count2/5

38 tools is heavy for a single server; each does earn its place across notebooks, sources, chat, studio artifacts, research, sharing, and server-health, but the surface is well past the 25-tool threshold and increases selection cost substantially.

Completeness5/5

Lifecycle coverage is excellent across every sub-domain: full notebook CRUD, source add/list/read/rename/delete/wait plus Play Books and Drive ingestion, chat ask/start/status/cancel/configure, studio generate/list/status/download/rename/delete/retry, research start/status/import/cancel, and share status/set/remove. Dead ends are rare and explicitly handled (e.g. await_upload for remote file uploads).

Maintenance

ActivityMaintained
ResponsivenessSlow