MCP Zotero
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOTERO_API_KEY | Yes | Your Zotero API key created at https://www.zotero.org/settings/keys | |
| ZOTERO_USER_ID | Yes | Your Zotero user ID obtained from the API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_collectionsB | List all collections in your Zotero library |
| get_collection_itemsC | Get all items in a specific collection |
| get_item_detailsC | Get detailed information about a specific paper |
| search_libraryC | Search your entire Zotero library |
| get_recentC | Get recently added papers to your library |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: get_collection_items retrieves items within a collection, get_collections lists collections, get_item_details provides details on a specific paper, get_recent shows recent additions, and search_library searches the entire library. The descriptions reinforce these distinctions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_collection_items, get_collections, get_item_details, get_recent, search_library). The naming is predictable and readable throughout, with no deviations in style or convention.
With 5 tools, the count is well-scoped for a Zotero library management server, covering core operations like listing, searching, and retrieving details. It is slightly lean but reasonable, as it includes essential functions without being overwhelming or too sparse.
The tool set covers read operations well (get, list, search) but lacks create, update, or delete capabilities for collections or items, which are typical in library management. This creates notable gaps that agents might need to work around, though the existing tools handle basic retrieval tasks adequately.