Fetch, edit, and publish markdown documents to demarkus servers directly from your Obsidian vault using the Mark Protocol.
- Fetch Document — pull a document from any demarkus server into your vault
- Publish Note — push the active note to a demarkus server with optimistic concurrency
- List Documents — browse a server's documents and fetch any of them
Fetched documents store mark-url, mark-version, and mark-etag in frontmatter so publishes know where to go and detect conflicts. Existing Obsidian frontmatter (tags, aliases, etc.) is preserved on both fetch and publish.
The plugin shells out to the demarkus CLI binary, which must be installed and available on your PATH (or configured in settings).
Install demarkus: https://github.com/latebit-io/demarkus
- Install the BRAT plugin in Obsidian
- Open BRAT settings and choose Add Beta Plugin
- Enter
latebit-io/obsidian-demarkus - Enable the plugin in Obsidian's Community Plugins settings
- Download
main.jsandmanifest.jsonfrom the latest release - Create a folder
<your-vault>/.obsidian/plugins/demarkus/ - Place both files in that folder
- Enable the plugin in Obsidian's Community Plugins settings
Open Settings > Demarkus to configure:
| Setting | Description |
|---|---|
| Server URL | Default mark:// host (e.g. mark://soul.demarkus.io) |
| Token | Capability token for publish operations (stored securely, never in vault files) |
| CLI Path | Path to demarkus binary (default: demarkus) |
| Insecure | Skip TLS verification for local dev servers |
All commands are available from the command palette (Cmd/Ctrl + P):
- Demarkus: Fetch document — prompts for a
mark://URL, fetches the document, and creates or updates a note in your vault underdemarkus/<host>/ - Demarkus: Publish note — publishes the active note to the server recorded in its frontmatter (or prompts for a URL if none)
- Demarkus: List documents — lists documents on your configured server and lets you pick one to fetch
The plugin bridges Obsidian and demarkus by shelling out to the demarkus CLI. Documents are stored in your vault under demarkus/<server-host>/ with their server path preserved. Frontmatter tracks the mark-url, version, and etag so the plugin can publish back with conflict detection.
AGPL-3.0-only