Archivum

The wiki that writes itself.

Repos carry code. They do not carry the reasoning: why a decision went the way it did, which approach already failed, what a customer actually asked for. Archivum is where that lives, and MCP is what makes it reachable.

Read the docs View on GitHub

Knowledge

Archivum

Synced

Markdown wiki

Project brief

Repo notes

Decision log

Release notes

Context capture

Convert notes, links, and repo docs into durable pages agents can actually use.

citationssearchagent context

Connected notes

Brief

Repo

Agent

Review

One command to start. No cloud account, no SaaS, and no data leaving your machine unless you point it at a hosted model.

What it does

Markdown pages stored on disk stay the source of truth — readable and backup-able outside the app.
A browser wiki with the Obsidian shape: folders, backlinks, wikilinks, autosave, search, and a graph view.
File and URL ingest turns sources into searchable wiki pages with source metadata.
A built-in MCP server so Claude Desktop, Claude Code, Cursor, or VS Code read the same notes you do.
Point the extraction and embedding providers at Ollama and nothing leaves the machine.

The loop

1Clone the repo and run ./install.sh (or .\install.ps1 on Windows).
2The installer writes .env, generates missing secrets, and starts the stack.
3Log in at http://localhost as the owner account you configured.
4Drop in documents and URLs; ingest turns them into linked wiki pages.
5Point your MCP client at the server so agents read and write the same wiki.

Install

Guided installer

git clone https://github.com/perceo-ai/archivum.git
cd archivum
./install.sh

Manual (Docker Compose)

cp .env.example .env
docker compose -f docker-compose.yml -f docker-compose.images.yml up -d --no-build

Requirements

Docker Engine 24+ with Docker Compose v2.
Node.js 20+.
An Anthropic key, OpenRouter key, OpenAI-compatible endpoint, or local Ollama setup.

Documentation

Overview Install