Loading
KIP MCP Server
io.github.dillanClaim this server
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Local command
npx -y [email protected]Credentials from the publisher
- SIGNALK_HOST — Signal K server host name or IP.
- SIGNALK_PORT — Signal K server port.
- SIGNALK_TLS — Set true if Signal K uses https/wss.
- SIGNALK_TOKEN — Signal K token, needed to write dashboards (or use SIGNALK_USER/PASSWORD).
- SIGNALK_USER — Signal K username, used with SIGNALK_PASSWORD instead of a token.
- SIGNALK_PASSWORD — Signal K password, used with SIGNALK_USER.
- KIP_URL — Override where KIP is served, if it is not the default.
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
SIGNALK_HOST=<value> SIGNALK_PORT=<value> SIGNALK_TLS=<value> SIGNALK_TOKEN=<secret> SIGNALK_USER=<value> SIGNALK_PASSWORD=<secret> KIP_URL=<value> claude mcp add io.github.dillan-kip-mcp-server -- npx -y kip-mcp-server@1.12.0Run in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.github.dillan-kip-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "SIGNALK_HOST": "<value>", "SIGNALK_PORT": "<value>", "SIGNALK_TLS": "<value>", "SIGNALK_TOKEN": "<secret>", "SIGNALK_USER": "<value>", "SIGNALK_PASSWORD": "<secret>", "KIP_URL": "<value>" } } }}claude_desktop_config.json
Local · npmPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
Local- Transport
- stdio
- Version
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ