About this integration
Local Zotero, MinerU, Obsidian literature workflow with transactional Analysis notes.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 3.0.2
- Package
- zotero-obsidian-mcp
- Last compatibility test
- Not independently tested
Connect your agent
zotero-obsidian-mcpThe qualified artifact is the documented local stdio package, not each supported client or Registry alias. An existing Obsidian vault and local Zotero API are prerequisites for their respective workflows; optional external MinerU use requires separate authorization review. No package, local application, or external service was executed.
Capabilities: Import and synchronize Zotero literature records and attachments, Extract PDF text through an optional MinerU workflow, Maintain Obsidian literature notes, indexes, analyses, and wiki pages, Preview and apply transactional vault writes with backup and rollback support
Connected profiles
Additional details
io.github.luffysolution-svg/obsidian-vault-mcp
Source ↗ · Checked 2026-09-173.0.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17OBSIDIAN_VAULT_PATH
Source ↗ · Checked 2026-09-17zotero-obsidian-mcp
Source ↗ · Checked 2026-09-193.0.2
Source ↗ · Checked 2026-09-19The client launches the pinned Python package as a local stdio process and supplies an Obsidian vault path; Zotero and optional MinerU operations have separately documented prerequisites.
Source ↗ · Checked 2026-09-19The base stdio configuration uses a local vault path and Zotero's local API, while optional MinerU processing may use a token and may send PDFs to an external service. Because authentication varies by optional workflow, it is classified as unknown rather than OAuth or client credentials.
Source ↗ · Checked 2026-09-19Configure uvx to launch zotero-obsidian-mcp 3.0.2 with serve --transport stdio and set OBSIDIAN_VAULT_PATH to an existing Obsidian vault.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19