Home / MCP registry index / io.github.mcp-dir/notebooklm-mcp

NotebookLM

io.github.mcp-dir/notebooklm-mcp in the official MCP registry. Endpoint https://api.mcp.ai/p_notebooklm. Source: github.com/mcp-dir/notebooklm-mcp.

The registry describes it as: Google NotebookLM via natural language: create notebooks, add sources (PDF, URL, YouTube) and ask gr

We read its 43 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http notebooklm-mcp https://api.mcp.ai/p_notebooklm

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "notebooklm-mcp": {
      "url": "https://api.mcp.ai/p_notebooklm"
    }
  }
}

VS Code

code --add-mcp '{"name":"notebooklm-mcp","type":"http","url":"https://api.mcp.ai/p_notebooklm"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

notebooklm_list notebooklm_notebook_create notebooklm_notebook_rename notebooklm_notebook_delete notebooklm_notebook_summary notebooklm_notebook_metadata notebooklm_ask notebooklm_history notebooklm_source_add notebooklm_source_list notebooklm_source_get notebooklm_source_fulltext notebooklm_source_guide notebooklm_source_rename notebooklm_source_refresh notebooklm_source_delete notebooklm_source_add_research notebooklm_generate notebooklm_artifact_list notebooklm_artifact_get notebooklm_artifact_poll notebooklm_artifact_suggestions notebooklm_artifact_rename notebooklm_artifact_retry notebooklm_artifact_delete notebooklm_download notebooklm_note_create notebooklm_note_list notebooklm_note_get notebooklm_note_rename notebooklm_note_delete notebooklm_share_status notebooklm_share_public notebooklm_share_add notebooklm_share_update notebooklm_share_remove notebooklm_share_view_level show_version report_bug connect toolkit_info marketplace authenticate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-notebooklm-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-notebooklm-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

YouTube and video MCP servers · Documents and PDF MCP servers