Zoteus
Related Servers
Alternatives to Zoteus
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server that lets AI assistants search, create, organize, and cite from a Zotero library.394MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI assistants to your Zotero library, enabling full-text PDF extraction and metadata search.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives AI agents read access to a Zotero library, enabling search, item metadata, collections, tags, notes, and full-text search of attached PDFs.MIT
- AlicenseAqualityDmaintenanceAn MCP server that gives any MCP-compatible assistant access to your Zotero reference library, enabling search, citation, bibliography generation, and .docx processing while keeping Zotero as the ground truth for references.91MIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables AI assistants like Claude to read and search your local Zotero bibliographic database directly from your machine.8MIT
- AlicenseAqualityAmaintenanceAn MCP server that lets AI assistants add papers and books to your Zotero library by DOI, arXiv ID, or ISBN, and manage your collections, tags, and items.5086 PyPI2MIT
TDQS
Scored across 34 tools
Most tools map cleanly to distinct resources and actions, but the set contains several near-overlapping pairs—zotero_fulltext/zotero_get_fulltext, zotero_attachment/zotero_attach_file, zotero_bibliography/zotero_format_bibliography, and manage_/list_ variants—that an agent could confuse. The descriptions do a strong job of explaining the differences, which keeps the ambiguity manageable.
The zotero_ prefix and a mostly verb_noun shape (search_items, get_item, merge_items) make the naming predictable. The pattern is not perfect: search_tools lacks the prefix, zotero_whoami is a command rather than a verb_noun pair, and noun-only names like zotero_fulltext and zotero_bibliography deviate from the dominant style.
At 34 tools, the server sits clearly above the 25-tool threshold that starts to overwhelm agent selection. Many clusters (fulltext, attachment, bibliography, list/manage) could be consolidated, though the broad Zotero scope and the search_tools discovery aid do make the size understandable.
The surface covers essentially the entire Zotero workflow: schema, import, item/collection/tag CRUD, trash and permanent delete, attachments, full text, PDF images, keyword/semantic search, export, bibliography, sync, deduplication, groups, tag audit, and scholarly citation lookup. I cannot identify a significant dead end or missing lifecycle stage.