Summary
cli-anything-zotero is the most powerful tool in our Zotero stack for imports, full-text search, notes and direct JS access. Because it is a Python CLI invoked over SSH, it cannot be used directly by MCP clients such as Kimi Code, Claude Desktop or Cline without custom shell wrappers. An official MCP-server wrapper would make the tool accessible to a much larger audience.
Observed workflow today
From the Linux AI client we call:
ssh windows-host "zotero-cli item get F5724CQV"
This works, but:
- The AI client cannot discover available tools/schema automatically.
- Each call incurs SSH startup overhead.
- Error handling and streaming must be managed manually.
Suggested solution
Ship a small cli-anything-zotero-mcp entry point (or an mcp subcommand) that exposes the existing CLI commands as MCP tools, e.g.:
item_get
item_notes
search_fulltext
note_add
item_citation
add_doi
js
The wrapper would reuse the existing JS-bridge backend and simply translate JSON-RPC calls into CLI invocations.
Context
Full comparison of Zotero tools (including why a Memory-MCP server helps manage several tools):
Why it matters
With an MCP wrapper, cli-anything-zotero could become the default Zotero backend for coding agents, combining the power of the JS bridge with the ergonomics of MCP tool discovery.
Summary
cli-anything-zoterois the most powerful tool in our Zotero stack for imports, full-text search, notes and direct JS access. Because it is a Python CLI invoked over SSH, it cannot be used directly by MCP clients such as Kimi Code, Claude Desktop or Cline without custom shell wrappers. An official MCP-server wrapper would make the tool accessible to a much larger audience.Observed workflow today
From the Linux AI client we call:
ssh windows-host "zotero-cli item get F5724CQV"This works, but:
Suggested solution
Ship a small
cli-anything-zotero-mcpentry point (or anmcpsubcommand) that exposes the existing CLI commands as MCP tools, e.g.:item_getitem_notessearch_fulltextnote_additem_citationadd_doijsThe wrapper would reuse the existing JS-bridge backend and simply translate JSON-RPC calls into CLI invocations.
Context
Full comparison of Zotero tools (including why a Memory-MCP server helps manage several tools):
Why it matters
With an MCP wrapper,
cli-anything-zoterocould become the default Zotero backend for coding agents, combining the power of the JS bridge with the ergonomics of MCP tool discovery.