wiki-loop-mcp
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., "@wiki-loop-mcpadd to wiki: today I learned about MCP server architecture"
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.
Prometheus Wiki Loop
Three small tools that turn any AI coding session — Claude Code, OpenCode, Codex, Claude Desktop, Kimi Desktop, Mavis/MiniMax Desktop, or a bare shell — into a contribution to a shared, human-readable, version-controlled knowledge base.
The Karpathy pattern, in shell. Plain markdown wiki, LLM-compiled, TF-IDF searchable, no vector database. Every session closes by writing what was learned into the wiki. The next session opens with the wiki already primed.
What's in the box
File | What it does | When it runs |
| Universal session-close hook. Reads a summary (file, stdin JSON, or fallback), enriches it with active KBD phase context, calls | End of every session (Stop hook, PreCompact hook, notify, or manual) |
| Session-prime companion. Detects active KBD phase from | Start of every session (SessionStart hook, or manual) |
| Zero-dependency Node stdio MCP server. Exposes 7 tools ( | Whenever the chat tool calls a tool |
All three scripts:
Are MIT licensed, < 500 lines each, zero non-stdlib dependencies
Source
~/.prometheus/.envautomatically so the LLM endpoint (openai-proxy, OpenAI, Anthropic, Groq, etc.) is configurable per environmentAlways exit 0 — a hook failure never breaks the calling tool
Related MCP server: WikiMCP
Install
# 1. Install the wrappers to ~/.local/bin (must be on PATH)
./scripts/install.sh
# 2. Seed the env file with your LLM endpoint
cat > ~/.prometheus/.env <<'EOF'
CLOUD_LLM_URL=https://api.openai.com/v1 # or http://localhost:8181/v1 for openai-proxy
LOCAL_LLM_URL=https://api.openai.com/v1
CLOUD_LLM_API_KEY=sk-...
PK_COMPILE_MODEL=gpt-4o-mini
PK_LINT_MODEL=gpt-4o-mini
PK_FOCUS_MODEL=gpt-4o-mini
EOF
# 3. Make sure pk is installed (from the prometheus-knowledge crate)
# and the prometheus-knowledge MCP server is running on port 8942.
# See: https://github.com/Prometheus-AGS/prometheus-knowledge
# 4. (Optional) Register the MCP server in your chat tool
# Claude Desktop, Mavis/MiniMax, Kimi Code CLI, Codex:
{
"mcpServers": {
"wiki-loop": {
"command": "/Users/gqadonis/.local/bin/wiki-loop-mcp"
}
}
}That's it. From this point:
Every Claude Code session begins with
last-open-snapshot.txtshowing your active KBD phase + focused wiki hits + pending skill-updatesEvery Claude Code session ends (or compacts) with the work written into the wiki
Codex, OpenCode, Kimi Code, Mavis/MiniMax Desktop — same wiki, different trigger surface
Chat surfaces (Claude Desktop, Kimi Desktop chat, Codex chat) — say "save this conversation to the wiki" and the agent calls
add_to_wikiautomatically
The full architecture
┌──────────────────────────────────────────────────────────────────┐
│ AI Tools (any of these) │
│ │
│ Claude Code Codex OpenCode Kimi Code │
│ ↓ ↓ ↓ ↓ │
│ Stop/PreCompact notify plugin /kbd-close skill │
│ ↓ ↓ ↓ ↓ │
│ ┌──────────────────────────────────────────────────┐ │
│ │ ~/.local/bin/kbd-close (universal) │ │
│ └──────────────────────────────────────────────────┘ │
│ ↓ │
│ ┌──────────────────────────────────────────────────┐ │
│ │ Detect KBD phase + enrich + pk ingest + log │ │
│ └──────────────────────────────────────────────────┘ │
│ ↓ │
│ ┌──────────────────────────────────────────────────┐ │
│ │ ~/.prometheus/knowledge/shared/wiki/*.md │ │
│ │ ~/.prometheus/learning-log/YYYY-MM-DD.jsonl │ │
│ │ ~/.prometheus/skill-updates/ │ │
│ └──────────────────────────────────────────────────┘ │
│ │
│ Chat surfaces (Claude Desktop, Kimi Desktop, Codex chat) │
│ ↓ "save this to the wiki" │
│ ┌──────────────────────────────────────────────────┐ │
│ │ ~/.local/bin/wiki-loop-mcp (MCP server) │ │
│ │ 7 tools: add_to_wiki, prime_context, ... │ │
│ └──────────────────────────────────────────────────┘ │
└──────────────────────────────────────────────────────────────────┘What it depends on
bash (for kbd-close / kbd-open)
node ≥ 18 (for wiki-loop-mcp, zero deps)
python3 (for the JSON extraction helpers in kbd-close)
pk CLI (from prometheus-knowledge) — compiled to
~/.prometheus/bin/pkor on PATHprometheus-knowledge MCP server running on
:8942(or override withPK_BINenv var)An LLM endpoint reachable by the chosen
CLOUD_LLM_URL(default: OpenAI; works equally with the local openai-proxy on:8181or any OpenAI-compatible service)
The related projects
This toolkit is one piece of the Prometheus Fabric, an open-source multi-repository platform for sovereign agentic AI built on BossFang (librefang). Related crates:
prometheus-knowledge— the RustpkCLI andpk-cherryMCP server this toolkit callssurreal-memory-server— the optional graph-memory + TaskStreams backendprometheus-skill-pack— the 280+ skill manifests and 4-layer PMPO pipeline that uses this toolkit for cross-session compoundingprometheus-entity-management— the React entity graph that consumes the wiki as a knowledge plane
License
MIT — see LICENSE.
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
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/Prometheus-AGS/prometheus-wiki-loop'
If you have feedback or need assistance with the MCP directory API, please join our Discord server