Looking for a NotebookLM MCP?
AutoContent MCP is an independent, unofficial alternative—not a Google or NotebookLM product. Use it to turn your sources into podcasts, infographics, slide decks, videos, and quizzes without leaving your AI assistant. It creates finished assets; it does not read your Google notebooks.
Uses your AutoContent API plan: from €29/month, and a podcast uses 10 credits.
Watch Codex turn three research sources into a two-host podcast and return the finished link.
An unofficial alternative
Audio and video overviews, slide decks and infographics are made with Google's Gemini Notebook (formerly NotebookLM), on accounts that AutoContent operates. AutoContent has no agreement with Google. Google can limit or stop this access at any time. The AutoContent MCP server gives your assistant the tools to request and monitor those generations. It does not connect to, read, or manage notebooks stored in your Google account.
Browse a complete public generation540 published outputs
The public library contains 108 projects, each with a podcast, infographic, slide deck, explainer video, and quiz. The examples below are four real outputs from “The Physics Behind Everyday Things”—nothing here is a mockup.
Open the complete public project
The Unseen Engine: The Physics of Everyday Life
The Physics Behind Everyday Things
A Field Guide to Everyday Wonders
This episode explores the intricate physics underlying everyday experiences, from toasters to smartphones, and how mechanics, thermodynamics, and electromagnetism shape the modern world.
Connect in one command
Connect the hosted MCP endpoint once. A valid AutoContent API key is required before the assistant can create assets; it uses the credits of your API plan.
Last verified: November 2, 2026
Claude Code
claude mcp add --transport http autocontentapi https://mcp.autocontentapi.com/mcpCodex
codex mcp add autocontentapi --url https://mcp.autocontentapi.com/mcpNo. AutoContent MCP is an independent product and is not affiliated with or endorsed by Google. Audio and video overviews, slide decks and infographics are made with Google's Gemini Notebook (formerly NotebookLM), on accounts that AutoContent operates. AutoContent has no agreement with Google. Google can limit or stop this access at any time. The MCP server does not connect to or read notebooks stored in your Google account.
For content generation, yes. AutoContent MCP gives Codex or Claude a similar source-to-content workflow: the assistant can create podcasts, infographics, slide decks, videos, and quizzes, monitor the job, and return the finished link. It is not a connector for Google notebooks.
No. If your goal is to query or manage existing Google NotebookLM notebooks, AutoContent MCP is not the right connector. It is designed to generate finished content assets from the sources you provide.
AutoContent MCP supports Codex CLI and Claude Code. Each client can connect to the same remote MCP endpoint with a one-line command.
Use MCP when people want to create content conversationally inside Codex or Claude. Use the REST API when your application needs direct requests, webhooks, scheduled jobs, or product-level automation.