notebooklm-py-wrapper-creates-porting-debt

Building a custom MCP server on top of notebooklm-py (v0.3.4) rather than notebooklm-mcp-cli creates ongoing maintenance debt — every new upstream capability requires manual porting. notebooklm-py is less actively maintained than notebooklm-mcp-cli. Prefer running upstream directly to eliminate ~500+ lines of custom tool code and get security hardening (CDP origin restriction, path traversal protection) for free.

Related

• 2026-04-04-oracle-001-self-architecture-analysis
• notebooklm-custom-wrapper-six-missing-capabilities
• docker
• openspace-mcp-123mb-is-98pct-upstream-demo-bloat
• notebooklm-mcp-cli-auth-two-file-format
• notebooklm-upstream-container-memory-1g-minimum
• notebooklm-mcp-cli-env-var-config-path
• notebooklm-mcp-container-requires-1gb-memory-not-512mb
• custom-notebooklm-wrapper-vs-upstream-tradeoff