An MCP server for the Zotero Web API — search, add, update, and manage Zotero items from any MCP-compatible client.
Zotero-MCP has 15 well-named tools with consistent verb_noun patterns (search_, get_, add_, update_, delete_, remove_). All tools have descriptions (avg ~120 chars, within baseline 34-392 range). Input schemas are present and typed for all tools. However, output schemas are NOT documented, the code shows API calls but no explicit return type definitions in tool registration. Parameter descriptions are present but minimal (avg ~50 chars vs baseline 72). Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). Missing dependency hints (e.g., 'search_items first if you only have a title'). Credentials are properly injected via environment variables, not exposed as parameters.
Add a new item to your Zotero library. Accepts item metadata (title, creators, publication details, etc.) and returns the newly created item with its key.
Add an arXiv preprint to your Zotero library by its arXiv ID or DOI. Automatically fetches metadata from arXiv.
Add an item to your Zotero library by its DOI. Automatically fetches metadata from CrossRef or PubMed.
Add a PubMed article to your Zotero library by its PMID. Automatically fetches metadata from PubMed.
Add an item to a collection.
Add a tag to an item.
Delete an item from your Zotero library by its key.
Output schemas not documented. Code shows API calls but tool registration does not declare return types. LLMs cannot plan downstream calls or extract required fields (e.g., item_key for chaining).
No error handling or recovery guidance. Tools fail silently or return raw HTTP errors. No categorization of retryable vs fatal errors. LLMs cannot self-correct or know when to retry.
No tool annotations despite clear risk levels. delete_item is DESTRUCTIVE but lacks destructiveHint. READ_ONLY tools lack readOnlyHint. Agents cannot reason about side effects or idempotency.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
List all items in a specific collection.
List all collections in your Zotero library.
Retrieve the full metadata for a single item by its Zotero item key.
List all tags in your Zotero library.
Remove an item from a collection.
Remove a tag from an item.
Search for items in your Zotero library by title, creator, tag, or other metadata. Returns matching items with their metadata.
Update an existing item in your Zotero library. Provide the item key and the fields to update.
Destructive operations (delete_item) lack confirmation or dry-run support. Agents can permanently delete items without safeguards.
Parameter descriptions are minimal (avg ~50 chars vs baseline 72). Missing format hints, constraints, and dependency documentation. E.g., 'creators' array lacks structure; 'updates' object in update_item lacks field documentation.