ai-wiki-service
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
ai-wiki-service
A self-synthesizing AI knowledge wiki (Karpathy LLM-wiki pattern). The successor to
ai-wiki-mcp: instead of the calling agent doing synthesis, this service does it itself.
Three parts:
UI — vanilla JS/HTML, served by the server (ingest box, file tree, wikilink graph).
Server — FastAPI HTTP API for the UI + a read-only FastMCP surface for external agents to trace the wiki. Writes only
raw/.Worker — a LangGraph agentic loop that, on each ingested raw document, runs the import + synthesis process against a configured model (via the LiteLLM proxy) and commits the result.
State (job queue + LangGraph checkpoints) lives in Postgres. The wiki itself is a git repo of markdown — one commit per import/synthesis run. A periodic lint pass is the correctness safety net; there is no human review gate.
See docs/plans/ for the implementation plan.
Commands
uv sync # install deps
uv run pytest # run tests (offline; DB tests need AIWIKI_TEST_DSN)
uv run ruff check src tests # lintFor the full local dev loop (rootless Postgres, env, running the server/worker, and the
manual end-to-end spikes), see CLAUDE.md.
Related MCP server: Predicate
Deployment (llm-server / VM 215)
Built as one image with two entrypoints; docker-compose runs it as three services
(ai-wiki-service-{db,server,worker}) on the existing app-net bridge.
# 1. Image is built + pushed to the Gitea registry automatically by CI on merge to main
# (.gitea/workflows/ci.yaml; bump pyproject version per PR). To build by hand instead:
# docker build -t 192.168.10.32:3000/jhonnold/ai-wiki-service:<ver> . && docker push …
# 2. One-time host provisioning (creates + git-inits the wiki tree, seeds from live ai-wiki):
bash deploy/bootstrap.sh # run on VM 215
# 3. Add the three services from deploy/docker-compose.snippet.yaml into
# ~/projects/llm-server/docker-compose.yaml, add the AIWIKI_* vars to its .env, then:
docker compose up -d ai-wiki-service-db ai-wiki-service-server ai-wiki-service-workerThe UI + read-only MCP are then at http://192.168.10.40:3011/app/ and …/mcp. The
worker auto-synthesizes each ingested source and runs a lint pass after every
AI_WIKI_LINT_AFTER_N syntheses. See .env.example for all settings.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Knowledge base for AI agents: search, read, tasks; write, correct, report outcomes via /mcp/write.
Shared persistent memory for AI agents to read, verify, continue, and connect knowledge.
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP
Shared project wiki for AI agents: read and write pages, next actions, and activity logs over MCP.
Related MCP Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables AI agents to compile, refine, and interlink knowledge into a persistent wiki, replacing RAG with structured, curated knowledge.1533 npm5MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that provides a self-improving knowledge graph with per-triple provenance and deterministic reasoning, enabling auditable, reproducible, and contradiction-aware answers for AI agents.-
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to maintain a personal knowledge wiki via MCP, allowing users to add sources and ask questions grounded in their research.4 npmMIT
- FlicenseNot gradedqualityCmaintenancePublic browse-first MCP server for AI capability discovery and grounded Agent feedback. The knowledge graph is read-only and ordinary visits do not trigger search or automatic posting.-