Self-hosted · MCP-native · Open core

Stop feeding notes to your AI.
Let your AI keep the notes.

Mycel is a knowledge base that agents maintain and humans trust. Connect Claude or any MCP agent — it files, links, and prunes your wiki while you watch it grow live. Every agent edit is reversible. Every source stays yours.

docker compose up · your Postgres, your markdown, your keys · no vendor can read a word

agent session · filing notes
nodes 0 · links 0
The wiki is a persistent, compounding artifact. The cross-references are already there. The contradictions have already been flagged. The synthesis already reflects everything you've read.

— Andrej Karpathy, the LLM Wiki pattern. Mycel is a production implementation of this pattern — with the safety rails the folder-of-files version can't have.

Independent project. Not affiliated with or endorsed by Andrej Karpathy.

The problem

Your knowledge tools weren't built for the age of agents.

Chats evaporate

That brilliant analysis your AI wrote last Tuesday? Gone, three hundred messages up. Conversations are where synthesis goes to die.

RAG re-discovers

Retrieval pipelines piece the same fragments together on every single question. Nothing accumulates. Nothing compounds.

Wikis rot

Notion and Obsidian assume a human does the gardening. Nobody does the gardening. Your vault is a graveyard of good intentions.

How it works

A wiki that tends itself. A human who stays in charge.

Three verbs, straight from the LLM Wiki pattern — industrialized.

Connect any agent

Point Claude Desktop, Claude Code, or any MCP client at your Mycel server. The agent reads your KB schema on arrival and becomes a disciplined librarian — 16 tools, full parity with the human editor.

mcp: read · search · file · link · lint

It ingests, links & lints

Drop in sources — the agent integrates them across pages, auto-links concepts, flags contradictions, and surfaces orphan pages and unwritten references as ghost nodes on the graph.

lint_kb → orphans · ghosts · contradictions

You watch. And undo.

Every edit streams to your screen live. Every agent change is grouped, attributed, and one-click reversible. Bulk deletions wait for your approval. Trust isn't a vibe here — it's a schema.

revert_group · approval gate · full history
Why Mycel

The parts you can't bolt onto a folder of files.

Karpathy's pattern runs on discipline. Mycel runs on guarantees — because it owns the database under the markdown.

Time-travel for agent edits

Agent reorganized 40 notes badly at 3am? One click restores all of them. Append-only history, group revert, per-block attribution.

The #1 fear of agent-managed knowledge, solved structurally.

Immutable raw sources

Sources are marked kind: raw and the server refuses agent writes to them. Synthesis can be wrong; your originals can't be.

Enforced by the server — not by prompt engineering.

A living graph

Force-directed, real-time, draggable. Ghost nodes show what you reference but haven't written — your knowledge frontier, visualized.

Zero external JS dependencies. It's 4KB of physics.

Hybrid search, honest zero

Postgres full-text + pgvector semantic, fused with RRF. New notes are searchable the second they're saved. Nonsense queries return nothing.

Agents that can't find what they wrote are useless.

Lossless markdown exit

Export to plain markdown with stable block anchors, edit anywhere — even in Obsidian — and re-import without losing history or links.

A knowledge base you can leave is one you can trust.

CJK-first editor

The block editor is engineered around IME composition — Korean, Japanese, and Chinese input never breaks mid-syllable, even during live agent sync.

Most AI editors get this wrong. We tested with 한글 first.
Compared

Same pattern, different guarantees.

Mycel DIY files + agent Notion AI RAG chatbots
Agent maintains the wikiYes — 16 MCP toolsYesAssists onlyNo wiki
Undo an agent's whole sessionOne clickgit, maybeNo
Immutable sources, enforcedServer-enforcedBy disciplineNo
Live view while agents workReal-timeReload filesPartial
Built-in health checks (lint)Orphans · ghosts · contradictionsPrompt it yourselfNo
Your data, your serverSelf-hostedYesTheir cloudUsually theirs
Lossless exportMarkdown + anchorsIt is filesLossy
Pricing

Free where it counts. Paid where it compounds.

The core is open and self-hosted forever. Paid tiers buy you the gardener, not the garden.

Seedling

For hackers and note-hoarders

$0forever

Open core · AGPL

  • Everything core: block editor, live graph, hybrid search
  • Full MCP tool surface, unlimited agents
  • Unlimited notes on your own Postgres
  • History, group revert, approval gate
  • Community support
Self-host now
Most popular

Grove

For people whose notes make money

$19/ month

or $149/year — 2 months free

  • Scheduled Gardener: a nightly agent that lints, links & files your inbox
  • Premium embeddings pack — tuned multilingual semantic search
  • Managed cloud instance or supported self-host
  • Obsidian vault live-sync (early access)
  • Priority support, 48h SLA
Start 14-day trial

Canopy

For teams growing a shared brain

$79/ month · up to 10 seats

then $8/seat · Enterprise: talk to us

  • Everything in Grove
  • Review workflows: agent changes gated per policy
  • SSO / SAML, audit log export
  • Slack & meeting-transcript ingestion
  • Dedicated onboarding
Contact sales
🌱 Founding Forester — $249 once, Grove for life

First 500 licenses only. Price locks before we plant the next feature. Counter is real.

Claim 1 of 500

Prices in USD. Self-hosted plans are licenses — your data never touches our servers. VAT handled at checkout.

FAQ

Fair questions.

What if the agent wrecks my knowledge base?
It can't — not permanently. Every agent change lands as an attributed, grouped, reversible transaction. Bulk destructive operations don't even execute: they queue for your approval. Worst case is noise, never loss. This is the core difference from pointing an agent at a folder of files.
Which AI agents work with it?
Anything that speaks MCP (Model Context Protocol): Claude Desktop, Claude Code, and the growing ecosystem of MCP clients. Agents get 16 tools and a KB schema note that teaches them your conventions on arrival.
How is this different from Obsidian or Notion with AI plugins?
Those are human-first tools with AI bolted on — the AI is a guest. In Mycel the agent is a first-class citizen with the same write path as you, plus guarantees no plugin can offer: enforced immutable sources, transactional edits, session-level undo, and a live view of what the agent is doing right now.
Is my data really private?
Self-hosted plans run entirely on your machine or server: your Postgres, local embeddings by default, no telemetry on your content. Export is lossless markdown, so leaving is always one command away. The free core is source-available under AGPL.
Did Karpathy build this?
No. Andrej Karpathy described the LLM Wiki pattern publicly and we think it's the right way to do knowledge in the agent era. Mycel is an independent production implementation — pattern credit is his, engineering blame is ours.

Plant it once.
It grows while you sleep.

Five minutes from docker compose up to an agent filing its first note into your graph.