A side-by-side look at the MCP Zotero and Hindsight MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Zotero for knowledge & memory work as a local process; choose Hindsight for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
ZOTERO_API_KEY, ZOTERO_USER_ID.get_collections, get_collection_items, get_item_details.HINDSIGHT_API_LLM_API_KEY.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Free | Free |
| Required env vars | ZOTERO_API_KEYZOTERO_USER_ID | HINDSIGHT_API_LLM_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 164 | 51,891 |
| Directory activity | 9 views 0 installs 0 upvotes | 13 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View MCP Zotero | View Hindsight |
get_collectionsList all collections in your libraryget_collection_itemsGet items in a specific collectionget_item_detailsGet detailed information about a papersearch_librarySearch your entire libraryget_recentGet recently added papersNo tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"kaliaboi-mcp-zotero": {
"command": "npx",
"args": [
"-y",
"mcp-zotero"
],
"env": {
"ZOTERO_API_KEY": "YOUR_ZOTERO_API_KEY_HERE",
"ZOTERO_USER_ID": "YOUR_ZOTERO_USER_ID_HERE"
}
}
}
}
{
"mcpServers": {
"vectorize-io-hindsight": {
"command": "npx",
"args": [
"-y",
"@vectorize-io/hindsight-coding-agents"
],
"env": {
"HINDSIGHT_API_LLM_API_KEY": "YOUR_HINDSIGHT_API_LLM_API_KEY_HERE"
}
}
}
}