NotebookLM for AI agents

NotebookLM Enterprise is Google's licensed, source-grounded notebook service for organizing sources and generating audio and text summaries in global-location deployments. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

AI and modelsOAuth 2.0MCP + RESTnotebooklm.google
AUDIT LOG · NOTEBOOKLMPOLICY: acme-support
09:41:07 · claude · u_8f2read
notebooklm.list_recent_notebooks
List Recent Notebooks✓ allowed · 212ms
09:41:08 · claude · u_8f2read
notebooklm.get_source
Get Source✓ allowed · 164ms
09:41:09 · claude · u_8f2write
notebooklm.create_notebook
Create Notebook✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
notebooklm.delete_sources
Delete Sources✕ blocked · policy: deny
EVERY NOTEBOOKLM CALL, ON THE RECORD
01 · USE CASES

What agents do in NotebookLM.

01

Add a source to a notebook

Add a document or text source to a notebook so it becomes part of its grounded context.

02

Check a notebook's sources

Look up which sources are already in a notebook before adding new ones, read-only.

03

Approve before deleting a notebook

Require approval before deleting a notebook, since it removes every source and summary in it.

02 · ACTIONS

11 NotebookLM actions, graded by risk.

Every NotebookLM action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

3

Look things up. Allowed by default.

  • notebooklm.get_source
    Get Source
  • notebooklm.get_notebook
    Get Notebook
  • notebooklm.list_recent_notebooks
    List Recent Notebooks

write

5

Create and change things. Allow, or ask the user first.

  • notebooklm.create_notebook
    Create Notebook
  • notebooklm.add_text_sources
    Add Text Sources
  • notebooklm.create_audio_overview
    Create Audio Overview
  • notebooklm.share_notebook
    Share Notebook
  • notebooklm.upload_source_file
    Upload Source File

destructive

3

Delete, cancel or archive. Ask first, or deny outright.

  • notebooklm.delete_sources
    Delete Sources
  • notebooklm.delete_notebooks
    Delete Notebooks
  • notebooklm.delete_audio_overview
    Delete Audio Overview
03 · HOW IT WORKS

NotebookLM in three steps.

  1. 01Your users connect NotebookLMThey sign in to NotebookLM on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, writes like “create Notebook” can wait for the user, and “delete Sources” can be denied outright.
  3. 03Any agent can actYour agent calls NotebookLM through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('notebooklm', {
  read: 'allow',
  write: 'ask',        // create_notebook
  destructive: 'deny',  // delete_sources
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How NotebookLM connects.

Users sign in to NotebookLM on Arc0 Connect and approve the scopes you request. Build with Arc0’s NotebookLM OAuth app, or bring your own so the NotebookLM consent screen names you. Tokens refresh automatically, and you can export them whenever you want.

The same NotebookLM connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
OAuth 2.0
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use NotebookLM from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

NotebookLM and Arc0, answered.

Q01

Can I use NotebookLM with Claude, ChatGPT or Cursor?

Yes. Connect NotebookLM to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the NotebookLM actions you allow.

Q02

How do users connect NotebookLM?

Users sign in to NotebookLM on Arc0 Connect and approve the scopes you request. Build with Arc0’s NotebookLM OAuth app, or bring your own so the NotebookLM consent screen names you. Tokens refresh automatically, and you can export them whenever you want.

Q03

Which NotebookLM actions can my agent take?

11 in total: 3 read, 5 write and 3 destructive, such as “create Notebook”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in NotebookLM?

Yes. Actions like “delete Sources” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call NotebookLM too?

Yes. The same NotebookLM connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug NotebookLM into your agent.

Your users connect NotebookLM once, under your brand. Your agent gets 11 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan