Skip to content

v4.6.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 19:50
· 65 commits to main since this release

Retry a failed generation without losing its id

retry_content, and POST /content/:id/retry, re-queue a failed Studio
artifact in place. A failed generation used to be final: the only recourse was
to delete and regenerate, which mints a new id and invalidates every reference
the caller held — a stored id, a poll loop already watching it, a queued
download. The retry keeps the id, so all of those survive.

Shipping it uncovered the half that made it unusable. list_content filtered
on completed artifacts, so a failed generation vanished from the listing:
indistinguishable from never having been asked for, and its id unreachable,
which left the new tool with nothing to be called with. The status has carried
three values since it was written — the filter was narrower than the type it
was filling. The listing now reports all three.

Two refusals rather than cheerful lies: a reply with no artifact row throws,
naming the artifact, instead of reporting a queued retry the caller would then
poll forever; and a media address is handed over only for a finished artifact,
because a half-written one is a download that fails later for no stated reason.

Protocol details read from teng-lin/notebooklm-py (MIT) and cited in the
code; the implementation is ours.

A UTCP interface, and 56 named operations

UTCP inverts MCP: there is no protocol server. A
client reads a manual once, then calls this REST API natively, with no
intermediary. GET /utcp serves that manual, generated from our own OpenAPI
specification and rebased on whatever address the request arrived at, so one
document serves a loopback install and a reverse-proxied one alike.

The manual exists because auto-conversion is not enough. A UTCP client will
convert an OpenAPI document it fetches, in JSON or YAML — but the reference
implementation keeps an operation only if it carries an operationId, and
every one of our 56 operations was unnamed. Pointed at our specification, a
client found no tools at all. All 56 are now named, with the names our MCP
tools already use, so search_passages is search_passages on both sides
rather than something synthesised from a URL path.

The second gap the manual closes is authentication. Our specification declares
a bearer scheme; the reference converter maps apiKey, basic and oauth2,
not that one, so a converted manual calls everything unauthenticated and every
call comes back 401. The published manual asks for the key as X-API-Key,
which this server has always accepted alongside the bearer form, in the exact
shape the client's own model defines. The key itself is never in the document —
only the literal ${NOTEBOOKLM_API_KEY}, which is how a client asks for a
value from its own environment.

Field names were taken from the reference client's source, not its prose: the
RFC and the published documentation disagree with each other on them. A
release guard regenerates the manual and fails on any difference, and refuses
outright an operation added without a name.

Releases update the published documents by themselves

npm version <x> now propagates the new version to all ten places that
restate it — the plugin manifest, the registry manifest, the site config, the
README, llms.txt, the AI catalogue, the roadmap, the OpenAPI specification
and the UTCP manual — and stages them into the version commit. Pushing that
commit triggers the docs deploy, which regenerates the specification and the
manual into the published static files. Nothing in the chain is a step anyone
has to remember, and three guards fail the release if one of them is skipped.

Gemini Notebook, written where people and crawlers read

Google renamed NotebookLM to Gemini Notebook in July 2026. Both names are now
in prose on every surface that advertises us — the README, the registry
manifest, the site metadata, llms.txt, the AI catalogue and all twelve blog
posts — because the old name is still what people search for and the new one
is what the product is called.

Three use-case posts, one per interface: calling the API from a UTCP client,
driving it from Python, and a literature-review agent over the MCP tools.
Every response shape in them was read out of the handlers before publishing.
A test holds each post to a contract — title and description lengths, a slug
matching its filename, tags, keywords, a summary break and at least one
internal link — so a post cannot ship unfit to be found.

Fixed

  • The site's social preview image was a 404 on every page. og:image and
    twitter:image had pointed at a file that was never committed, so every
    share of every page rendered blank. The card now exists, and a test fails if
    the configured image is absent from disk.
  • The published OpenAPI specification was frozen at version 1.5.9, with 27
    of the 56 routes.
    website/static/openapi.yaml was a hand-maintained
    second copy that nobody had regenerated since 24 October, so the document an
    AI client or a UTCP converter actually fetches described an API two years of
    releases behind the code. A copy nobody regenerates is worse than no copy,
    because it answers confidently and wrongly. The duplicate is gone; the site
    now generates it, and the manual, on every build.


Install / upgrade: npm i -g @roomi-fields/notebooklm-mcp@4.6.0

Full changelog: https://github.com/roomi-fields/notebooklm-mcp/blob/main/CHANGELOG.md