NotebookLM Ops

Manage NotebookLM MCP auth lifecycle on Linux by automating GUI startup, auth refresh, status check, and cleanup for frequent cookie expiry.

Automate operations for NotebookLM MCP in environments where Google session cookies become invalid quickly.

This skill solves repeated manual auth refresh by automating:

• GUI stack startup,
• navigation to NotebookLM,
• auth refresh via CDP,
• MCP sanity checks,
• full cleanup on shutdown.

Run commands from /home/moltuser/clawd.

Requirements / dependencies

• Linux host with Chromium and CDP (--remote-debugging-port=9222).
• Virtual display stack: Xvfb + openbox + x11vnc.
• Working scripts used by this skill:
  • /home/moltuser/clawd/scripts/notebooklm-remote-gui.sh
  • /home/moltuser/clawd/scripts/refresh-google-mcp-cookies.sh
  • /home/moltuser/clawd/scripts/notebooklm-on.sh
  • /home/moltuser/clawd/scripts/notebooklm-off.sh
• NotebookLM MCP configured in mcporter (notebooklm-mcp).

One-time login

A one-time manual login in Chromium to Google/NotebookLM is required. After that, this skill keeps refresh automated by reusing the same browser profile/session.

Turn NotebookLM ON

Execute:

bash

/home/moltuser/clawd/skills/notebooklm-ops/scripts/notebooklm-on.sh

Required sequence:

1. Start GUI/CDP stack (Xvfb + openbox + x11vnc + Chromium).
2. Navigate the current tab to https://notebooklm.google.com/.
3. Wait for load.
4. Refresh NotebookLM auth via CDP.
5. Reload NotebookLM MCP auth and run sanity check (notebooklm-list).

Turn NotebookLM OFF

Execute:

bash

/home/moltuser/clawd/skills/notebooklm-ops/scripts/notebooklm-off.sh

Stop Chromium and related GUI processes (x11vnc/Xvfb/openbox), then clean leftovers.

Check status

Execute:

bash

/home/moltuser/clawd/skills/notebooklm-ops/scripts/notebooklm-status.sh

Smoke test

Execute:

bash

/home/moltuser/clawd/skills/notebooklm-ops/scripts/notebooklm-smoke.sh

Expected result: notebook list returns "status": "success".

Failure handling

If auth refresh fails:

1. Re-run NotebookLM ON once.
2. If still failing, ask user to log in at https://notebooklm.google.com/ in the same Chromium profile via VNC.
3. Re-run NotebookLM ON and smoke test.