In-depth architectural comparison of the Zotero Library MCP and Zotero MCP Local MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Zotero Library MCP
Research · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Zotero MCP Local
Research · Local stdio
Quality: 33/100 (Emerging) | Auth: No auth required
Verdict Summary: Choose Zotero Library MCP if you need specialized Research tools running via a local process. Choose Zotero MCP Local if your workspace requires Research integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Zotero Library MCP when:
You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: ZOTERO_LIBRARY_ID, ZOTERO_API_KEY.
Zotero Library MCP is categorized under Research and uses a local stdio subprocess. In contrast, Zotero MCP Local belongs to Research using local stdio subprocess. Select Zotero Library MCP when you need capabilities focused on research and Zotero MCP Local when you require tools for research.