AutoWiki Agent
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AutoWiki AgentInitialize workspace at ~/Desktop/MyBrain"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🧠 AutoWiki Agent: The Autonomous Knowledge Base Compiler
Stop letting LLMs hallucinate over your notes.
AutoWiki Agent is a deterministic Model Context Protocol (MCP) server that compiles any LLM-readable text — transcripts, articles, contracts, notes — into a strict, verifiable, graph-based knowledge base.
No silent overwrites. No hallucinated facts. No lost sources. Just pure, traceable knowledge evolution.
v2.0 — Autonomous Architecture. Unlike v1, the server itself drives the LLM through deterministic chunking and parallel extraction of 6 epistemology primitives. The client agent is reduced to a thin pipe.
🔥 The Problem With AI Agents Editing Your Wiki
When you ask an AI to "update my wiki," it usually fails:
❌ Silent Overwrites: It deletes old (but vital) facts to make room for new ones.
❌ Hallucinations: It bridges knowledge gaps by inventing compromises.
❌ Lost Sources: You have no idea which PDF or web search a specific sentence came from.
❌ Schema Drift: Every agent invents its own entity shape; the wiki becomes a junk drawer.
AutoWiki Agent fixes all of this.
Related MCP server: Deliberate Reasoning Engine
🛡️ Core Features
1. Bottom-Up Epistemology (6 Primitives, Not Categories)
AutoWiki rejects hard-coded "Client" or "Pain Point" types. Instead, every chunk is parsed into 6 universal epistemology primitives:
Primitive | Schema | What It Captures |
Document DNA |
| Format, primary intent, tone (one-shot per file) |
Identifiers |
| Names, jargon, entities (with normalization) |
Quantifiers |
| Numbers, dates, metrics, units |
Relations |
| Subject → action → target graph edges |
Directives |
| Tasks, promises, obligations, warnings |
Unknowns |
| Explicit knowledge gaps and open questions |
2. Server-Driven LLM Calls
The server calls the LLM directly via HTTP. The client agent does not need to perform extraction itself. This means:
Deterministic chunking via
tiktoken(1000 tokens / 150 overlap)Parallel sampling (5 concurrent requests per chunk)
Strict Pydantic schema validation with automatic retry
Pagination (
start_chunk/max_chunks) to avoid timeouts
3. Iron Standard Source Protocol
Every fact in /wiki is anchored to a Source Passport in /inbox. No source — no fact.
4. Knowledge Evolution Protocol
Facts are never deleted. Updates are documented inline (*(Evolution: previously described as...)*). Contradictions are flagged with #NEEDS_HUMAN_RESOLUTION, never silently resolved.
5. Gatekeeper Filter
Only entities explicitly extracted from a chunk may "own" facts in that chunk. Anything else is bucketed into a Document_* container. Prevents cross-contamination of unrelated entities.
6. Git-Backed Audit Trail
Every semantic update is committed to a local Git repository. Full history, no overwrites.
7. MCP Native
Drop-in integration with Claude Desktop, Cursor, Gemini CLI, Windsurf, Roo Code, and any MCP-compatible client.
🚀 Quickstart
1. Install
git clone https://github.com/time-scout/autowiki-agent.git
cd autowiki-agent
pip install -e .2. Configure
cp .env.example .env
# Edit .env and set LLM_API_KEY, LLM_BASE_URL, LLM_MODELThe server expects an OpenAI-compatible chat completions endpoint.
3. Connect your MCP client
Add this to Claude Desktop, Cursor, Gemini CLI, Windsurf, or Roo Code:
{
"mcpServers": {
"autowiki": {
"command": "autowiki",
"args": ["start"]
}
}
}4. Initialize and use
Talk to your AI client:
"Initialize my workspace at ~/Desktop/MyBrain. Then process everything in /inbox."
Watch what happens:
AutoWiki sets up
/inbox,/wiki,/archive,/.autowiki.Drop a file into
/inbox(any text/markdown/JSON).Call
autowiki_ingest_document— the server chunks, calls the LLM 5x in parallel per chunk, validates against Pydantic schemas, retries on failure.Knowledge graph is committed to
/wikiand Git.
📁 Workspace Layout
<workspace>/
├── inbox/ # Drop raw sources here (text, md, json)
├── wiki/ # Compiled knowledge base (one .md per entity)
├── archive/ # Processed sources (auto-moved)
└── .autowiki/ # Internal SQLite state🛠 MCP Tools Exposed
Tool | Purpose |
| Returns init status (call this first) |
| Initializes the workspace |
| Chunks + LLM extraction + commit (paginated) |
| Generates Iron Standard filename |
| Lists files in |
| Reads entity from |
| Writes facts to |
📜 Technical Documentation (ADR)
Detailed architectural decisions live in docs/:
🆚 v1 vs v2 (Migration Note)
This is v2.0. The original v1 release is preserved at time-scout/autowiki-daemon for historical reference.
Aspect | v1 (Daemon) | v2 (Agent) |
Chunking | Done by the LLM agent | Deterministic |
Entity extraction | Agent-driven, ad-hoc | Server-driven, 6 fixed primitives |
LLM calls | ~2 (extract, compare) | 5 parallel per chunk + DNA per file |
Schema | 2 Pydantic models | 6 Pydantic models |
Concurrency | Single-writer | 5 concurrent LLM calls per chunk |
Pagination | None |
|
Entity filter | None | Gatekeeper: only chunk-local entities |
Working language | English | Ukrainian (UI/logs), English (prompts), source-locale (facts) |
⚖️ License
Distributed under the MIT License. See LICENSE for more information.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/time-scout/autowiki-agent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server