Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for researchers and knowledge workers who already live in NotebookLM: test it on a non-sensitive notebook first and see whether MCP access actually speeds up source collection, briefing generation, or study workflows.
Where this stands now
jacob-bd/notebooklm-mcp-cli ranks #216 of 2304 tracked Radar items by composite score (8.4 against a section median of 5.2). The section currently carries 1197 Bronze, 645 Gold, 462 Silver. RepoRadar has retained observations for this record since 2026-06-20 (99 days in the current window). Signal extremes versus the section: novelty at the 79th percentile.
Who should use it
Who should skip it
Skip jacob-bd/notebooklm-mcp-cli if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
jacob-bd/notebooklm-mcp-cli is tracked by RepoRadar as an MCP server in the Radar section. First seen 2026-06-20; the source record was last checked on 2026-06-20. The current verdict is 'watch' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, jacob-bd/notebooklm-mcp-cli is strongest on workflow potential (9.2) and open-source/build quality (8.4) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The jacob-bd/notebooklm-mcp-cli record combines a 8.4/10 composite score with separate popularity (16.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It relies on undocumented NotebookLM internals and browser-cookie-based authentication, so use it with an account and notebook scope you can afford to rotate if Google changes the flow or invalidates access.