package
Minimal MCP server that exposes KIP (Knowledge Interaction Protocol) tools over stdio.
npm install @ldclabs/kip-mcp-serverGitHub-flavored package documentation.
Across all versions.
Download trend unavailable.
Runtime metadata.
Minimal MCP server that exposes KIP (Knowledge Interaction Protocol) tools over stdio.
This server is a thin bridge:
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).This package ships documentation as MCP resources:
kip://docs/Instructions.mdkip://docs/KIP.mdkip_bootstrap: Returns a ready-to-inject system prompt for KIP usage.KIP backend implementation: https://github.com/ldclabs/anda-db/tree/main/rs/anda_cognitive_nexus_server
Start the backend:
docker run -d \
--name anda_kip \
-p 8080:8080 \
-e API_KEY=your_secret_key \
-v $(pwd)/db:/app/db \
ghcr.io/ldclabs/anda_cognitive_nexus_server_amd64:latest \
local --db /app/dbThen run this MCP server (stdio) and point it at the backend endpoint:
export KIP_BACKEND_URL="http://127.0.0.1:8080/kip"
export KIP_API_KEY="your_secret_key"
npx -y @ldclabs/kip-mcp-serverNotes:
KIP_BACKEND_URL is a single HTTP endpoint that accepts a JSON body like { "method": "execute_kip", "params": ... }./kip depends on your backend route. If unsure, check backend docs/logs and update the URL accordingly.API_KEY, this MCP server uses KIP_API_KEY (sent as Authorization: Bearer <key>).KIP_BACKEND_URL="http://127.0.0.1:8080/kip" npx -y @ldclabs/kip-mcp-servernpm i -g @ldclabs/kip-mcp-server
KIP_BACKEND_URL="http://127.0.0.1:8080/kip" kip-mcp-servercd mcp/kip-mcp-server
npm i
KIP_BACKEND_URL="http://127.0.0.1:8080/kip" npm run devRequired:
KIP_BACKEND_URL: HTTP URL for the KIP backend endpoint.Optional:
KIP_API_KEY: sent as Authorization: Bearer <key>KIP_AUTH_HEADER: overrides the Authorization header completely (e.g. Bearer ... or a custom scheme)KIP_TIMEOUT_MS: request timeout in milliseconds (default 30000)This MCP server runs over stdio, so most MCP clients can launch it with a command, args, and env.
Add a server entry to Claude Desktop config (macOS path shown):
~/Library/Application Support/Claude/claude_desktop_config.jsonExample:
{
"mcpServers": {
"kip": {
"command": "npx",
"args": ["-y", "@ldclabs/kip-mcp-server"],
"env": {
"KIP_BACKEND_URL": "http://127.0.0.1:8080/kip",
"KIP_API_KEY": "your_secret_key"
}
}
}
}Restart Claude Desktop after editing the file.
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:
npx-y @ldclabs/kip-mcp-serverKIP_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.
Look for a section named like “MCP Servers” / “Tools” / “Server (stdio)”.
Use the same launch parameters:
command: npxargs: -y @ldclabs/kip-mcp-serverenv: KIP_BACKEND_URL (+ optional auth vars)By default this package serves bundled docs from docs/.
Optional:
KIP_REPO_ROOT: if set, the server will additionally try loading Instructions.md.Estimated unpacked size across 56 packages.
15.6 MB
Includes dependencies.