wiki-mcp-serverlisted

Run a kata wiki as a Model Context Protocol (MCP) server over stdio. Any MCP-aware agent (Claude Code, Cursor, Continue, another kata acting as a federation client) can connect and call exposed read-only tools (wiki-search in Phase 0; wiki-query / wiki-graph / wiki-spec-preflight in Phase 1+). Read-only by design — write skills are never exposed across the MCP boundary.
litianyi-007/kata · ★ 0 · AI & Automation · score 73

Install: claude install-skill litianyi-007/kata

# wiki-mcp-server The first half of v1.12 cross-wiki federation: a kata wiki advertises itself to other MCP clients as a queryable knowledge base. The second half (the federation client side that consumes other wikis' MCP servers) ships in v2.10.0 / Phase 2. ## When to use - **Cross-wiki federation** (the original v1.12 use case) — kata A's `wiki-query` skill fans out to kata B by spawning B's `mcp_server.py` as a subprocess - **Non-kata MCP client integration** — Claude Code / Cursor / Continue can use kata as a search backend even if they don't ship with kata - **Multi-wiki workflows on one machine** — register N kata wikis as N separate MCP servers in your client's settings; each shows up as a distinct tool surface Skip if: - You only have one kata wiki and only use it via Claude Code slash commands (`/kata:wiki-search` etc) — the slash commands hit the scripts directly without MCP overhead - You're worried about read-then-write — the MCP surface is intentionally read-only; for write workflows use the regular skills ## Phase scope (v2.9.0) Exposed tools: | Tool | Status (v2.9.0) | Notes | |---|---|---| | `wiki-search` | ✓ shipped (v2.8.0) | 3-pass deterministic search; tier filter; tag/type filter | | `wiki-graph` | ✓ shipped (v2.9.0) | Read subset — neighbors / shortest-path / hubs / orphans / cluster / stats. `--apply`-style writes NOT exposed | | `wiki-spec-preflight` | ✓ shipped (v2.9.0) | Advisory candidates only. `--enforce` deliberately NOT