CMDS Zotero
unlistedby Yohan Koo (CMDSPACE)
Connect verified Zotero sources, citations, annotations, and literature notes to your vault.
CMDS Zotero
Connect Zotero sources, citations, annotations and literature notes with verified identities and preservation-aware imports.
Public source: 0.2.0. Local 0.3.0 development: not yet published. No GitHub release or Community Plugins listing as of 2026-09-14.
Obsidian 1.7.2+ | Desktop only.
0.3 development preview
- Rebuild a local Better BibTeX index and resolve canonical source/PDF identities.
- Insert citations and bibliography; review references and annotations in sidebars.
- Preview a single literature-note import and preserve human-owned content.
- Find citing notes and opt-in peer-vault references without writing to Zotero.
Install and first use
Public main currently builds 0.2.0, not the local 0.3 implementation described in the manual. Use the public 0.2 baseline guide when trying the available source. There is no public 0.3 install path yet; the 0.3 manual is a development preview, not a promise that public-clone builds include those features.
Read the manual
Privacy and limits
No published release or Community installation yet. Unpublished local 0.3 features are not the separate 0.4 work. Group libraries, interactive picker acceptance and Hookmark round trips remain environment-specific tests. Existing templates are not drop-in compatible. Batch update does not ask per note.
Citekey completion uses [@ by default. Completion, tag-exclusion and heading-highlight preferences are not yet exposed in the settings UI.
Development
npm ci
npm run lint
npm run typecheck
npm test
npm run build
These commands build whichever checkout you actually have. Public main is 0.2.0; they do not fetch unpublished 0.3 code.
Changelog
Credits and license
Yohan Koo (CMDSPACE), https://cmdspace.work. MIT, LICENSE.
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.