Demarkus is a protocol and toolkit for publishing markdown with version history, capability-based access, and QUIC transport. Humans and agents read and write the same store.
Start here
Give your agent memory. There is nothing to configure: the plugin spawns a local server, mints its own token, and wires up the tools. In Claude Code:
/plugin marketplace add latebit-io/demarkus
/plugin install demarkus-memory@demarkus
In pi:
pi install npm:pi-mcp-adapter
pi install ./demarkus/plugins/pi-memory
Both share the same ~/.demarkus state, so they coexist on one machine. Agent memory →
Ready to share it? One command turns a fresh Linux host into a whole knowledge system: world server, broker, reading room, self-hosted login, HTTPS, and the indexing agent.
curl -fsSL https://raw.githubusercontent.com/latebit-io/demarkus/main/install-stack.sh | sudo bash
No DNS setup, no accounts. The five-minute appliance →
One protocol, three scales
Personal
Local memory
A server on your own machine holding your agent's memory and your notes. No account, no cloud, no network exposure.
Team
A shared world
One server a group reads, a reading room for humans, MCP for agents. Tokens per person, or the appliance's built-in login.
Enterprise
A knowledge system
Many worlds behind one broker, your identity provider in front. Teams join with one command; the broker mints per-world tokens.
Store, verbs, history, and MCP surface are identical at every tier. Only reach and identity change, so moving up is a deployment change rather than a migration. Compare the tiers →
The tiers compose: a developer runs a personal soul and joins the org system in the same agent. The agent captures to the soul as it works, and /promote lifts a ready note up through a curation gate; /soul-refresh pulls the authoritative copy back as it changes. How knowledge flows →
What Demarkus is
Demarkus implements the Mark Protocol: versioned markdown served over QUIC. It is:
- Read-only by default: no writes without explicit auth tokens
- Version-preserving: every change is kept, nothing is deleted
- Privacy-first: no tracking, no cookies, no user agents logged
- Self-hostable: one static binary, no dependencies
- Graph-aware: persistent document graph with backlink queries across sessions
- OKF-compatible: interoperates with Open Knowledge Format v0.1
Tools
| Tool | Purpose |
|---|---|
demarkus-server |
Serve a directory of markdown files |
demarkus |
CLI: fetch, list, publish, edit, graph, lookup, okf |
demarkus-tui |
Terminal browser with graph view |
demarkus-mcp |
MCP server for LLM agents: tools, resources, prompts |
demarkus-agent |
Indexing agent: crawls worlds, aggregates the graph, publishes hub indexes |
demarkus-broker |
OIDC-fronted MCP gateway composing many worlds into one system |
demarkus-library |
Web reading room with the AI librarian |
demarkus-token |
Generate capability-based auth tokens |
demarkus-publish |
Write directly to the store for read-only server installs |
Install
- Five-minute appliance: the whole system on one host
- macOS · Linux · Windows (WSL2) · Docker
- OpenClaw: ClawHub skill for OpenClaw agents
- Obsidian plugin: fetch and publish via BRAT
Learn more
- About the Mark Protocol
- The library and the librarian
- Security model: attack surface, hardening, threat model
- Ecosystem: browsers, plugins, and tools that speak Demarkus
- Soul: the project’s live AI memory
- Public hub: discovery index at
mark://hub.demarkus.io - GitHub