Minimal MCP server that exposes KIP (Knowledge Interaction Protocol) tools over stdio.
This server is a thin bridge:
MCP client (Claude / VS Code / Cursor / etc) -> this package (stdio)
this package -> your KIP backend (HTTP)
Requirements
Node.js >= 18
What it provides
Tools
execute_kip: Execute one or more KIP commands against your backend. Important: clients should inject kip_bootstrap (or load kip://docs/Instructions.md) so the agent can use KIP correctly.
list_logs: List backend log entries (if your backend implements it).
Resources
This package ships documentation as MCP resources:
kip://docs/Instructions.md
kip://docs/KIP.md
Prompt
kip_bootstrap: Returns a ready-to-inject system prompt for KIP usage.
VS Code itself does not ship a single built-in MCP UI across all distributions, but several MCP-capable extensions support the same stdio-style server definition.
Use your extension's UI/settings to add an MCP server:
Command: npx
Args: -y @ldclabs/kip-mcp-server
Env: KIP_BACKEND_URL, KIP_API_KEY (optional)
If your extension uses a JSON setting (often named mcpServers), the Claude example above typically works with minimal changes.
Other MCP apps (Cursor / etc.)
Look for a section named like “MCP Servers” / “Tools” / “Server (stdio)”.
Use the same launch parameters:
command: npx
args: -y @ldclabs/kip-mcp-server
env: KIP_BACKEND_URL (+ optional auth vars)
Bundled docs (Resources)
By default this package serves bundled docs from docs/.
Optional:
KIP_REPO_ROOT: if set, the server will additionally try loading Instructions.md.