custom-notebooklm-wrapper-vs-upstream-tradeoff
The custom 42-tool notebooklm-py-based wrapper offered granular one-action-per-tool design but required manual porting of every upstream feature and tracked a less actively maintained library. Replacing with upstream notebooklm-mcp-cli directly eliminates all custom code, adds 20 net-new capabilities (including studio_revise, cross_notebook_query, batch, pipeline), and reduces future maintenance to pip install --upgrade. The trade-off is tool-name consolidation (e.g., 4 source_add_* tools → 1 source_add with source_type param) requiring skill rewrites.
Related
- notebooklm-mcp-v2-upstream-gains-20-net-new-capabilities
- notebooklm-py-wrapper-creates-porting-debt
- notebooklm-custom-wrapper-six-missing-capabilities
- notebooklm-custom-wrapper-capability-gaps-vs-upstream
- docker
- notebooklm-mcp-v2-upstream-replaces-custom-wrapper
- notebooklm-upstream-net-new-capabilities-v0517
- notebooklm-mcp-cli-consolidated-tool-architecture
- notebooklm-mcp-cli-replaces-custom-wrapper-zero-debt
- notebooklm-mcp-cli-upstream-replaces-custom-wrapper
- notebooklm-mcp-upgrade-replace-library-not-wrap
- replace-custom-notebooklm-mcp-with-upstream-notebooklm-mcp-c