@xbghc/zotero-mcp
Related Servers
Alternatives to @xbghc/zotero-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables interaction with a locally running Zotero Desktop library via MCP, including search, collections, tags, BibTeX export, citations, attachment full-text lookup, and explicitly confirmed write operations.MIT
- AlicenseNot gradedqualityAmaintenanceEnables searching, reading, annotating, and managing a Zotero library from any MCP client.AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceMCP server for interacting with a Zotero library via the local API. Enables searching, retrieving, creating, updating, and deleting Zotero items, managing collections and tags, and generating citations.-
- AlicenseAqualityAmaintenanceEnables MCP clients to search a Zotero library, read items, take notes, organize collections, and perform semantic search over PDFs.8MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables LLM clients to browse and query your Zotero library through tool calls. Provides access to Zotero-specific functions like listing open tabs, searching items, and browsing collections via a local MCP server running inside Zotero.1-
- AlicenseNot gradedqualityAmaintenanceEnables Zotero 10 library management via MCP, allowing search, metadata retrieval, annotation and collection management, and optional write operations (notes, tags, metadata, items) through a local Streamable HTTP endpoint.MIT
TDQS
Scored across 22 tools
Most tools target distinct resources and actions (e.g., get_item vs. get_item_fulltext vs. download_attachment). A few overlapping retrieval paths exist (search_items with includeTrashed vs. get_trash_items) but descriptions clarify their purposes.
All tool names use snake_case, but the verb pattern is inconsistent: 'get_' is used for both single items and lists (get_trash_items, get_recent_items) while 'list_' is reserved for collections/tags. This mix of get/list for list-style operations makes naming less predictable.
At 22 tools, the count is in the 'heavy' range (16-25) and feels borderline. Each tool has a distinct purpose, but the breadth may overwhelm agents; some operations could be consolidated (e.g., tag and collection membership updates).
Core CRUD for items and collections is covered, and there are useful extras like full-text search and bibliography export. However, notable gaps remain: no tool to remove tags from an item, remove an item from a collection, or restore items from trash. These missing operations could cause agent failures in common workflows.