notebooklm-mcp vs xiaozhi-esp32-server
notebooklm-mcp: NotebookLM REST API + MCP server provides a production-grade automation layer for Google NotebookLM. It offers 33 documented HTTP endpoints for integration with workflow tools like n8n, Zapier, and Make, as well as an MCP server for use with Claude Code, Cursor, and Codex. Key features include citation-backed Q&A, full Studio content generation (audio, video, infographic, report, presentation, data table), multi-account rotation with auto-reauth, and batch processing capabilities.; xiaozhi-esp32-server: This project develops a smart terminal software and hardware system based on human-machine symbiosis intelligence, serving as a backend for the open-source smart hardware project xiaozhi-esp32. It is implemented in Python, Java, and Vue, supporting various protocols and features like voiceprint recognition and a knowledge base.
TL;DR
Automate batch Q&A on large document collections with citation verification
- You own xiaozhi-esp32 hardware and want to host your own backend instead of a shared one.
- You want MQTT+UDP or WebSocket, MCP endpoints, voiceprint recognition and a knowledge base.
- You want a choice between a minimal no-database install and a full install with a web console and multi-user management.
- You have no ESP32 device: it is not useful without compatible hardware.
- You need production use: the README says it is incomplete and has not passed a network security evaluation.
- You cannot work from mainly Chinese documentation.
Side-by-Side Comparison
Features
Use Cases
Best For
FAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.