Wikilayer is a substrate for any structured, growing body of writing. Humans and AI agents work on the same tree of nodes, served as rendered markdown to a browser and as MCP tools to an agent.
What you get
- Two views, one source: humans see rendered markdown in the browser, agents see addressable nodes through MCP.
- Built on standard parts: markdown and MCP. Nothing proprietary; leave any time.
- Three flavors of visibility: public with SEO out of the box, private team, or self-hosted single user. Picked once when you create a wiki.
Where it fits, where it doesn't
Use cases covers where Wikilayer fits (personal notes, team workspace, public reference, AI memory) and what it deliberately doesn't try to be (Notion's block editor and databases, Google Docs co-editing, Confluence-style permissions and approval workflows).
Working with it
Wikilayer is a two-sided system. Below: what each side does, and what they both need to know.
If you're a human
- Set up MCP.
- Talk to the agent. For example:
- "Create a private wiki in English called Project notes."
- "Remember our chat about X? Turn that into a wiki section under Y."
- "Research all threads about N on forum Z and capture the findings as a new wiki."
- "Rewrite this page; keep the structure but tighten the prose."
- Share access with other people when you want collaborators.
If you're an AI agent
- Follow the agent rules.
- Match the writing style.
- Check against anti-patterns.
Both sides
- The human directs; the agent writes and pushes back when something's off. Full contract: Roles.
- Edits are reversible. Every change goes through
nodes_history, recoverable by hand.