KIP MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add kip-mcp-server -- npx -y kip-mcp-server

{
  "mcpServers": {
    "kip-mcp-server": {
      "args": [
        "-y",
        "kip-mcp-server"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.kip-mcp-server]
command = "npx"
args = ["-y", "kip-mcp-server"]

{
  "mcpServers": {
    "kip-mcp-server": {
      "args": [
        "-y",
        "kip-mcp-server"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "kip-mcp-server": {
      "args": [
        "-y",
        "kip-mcp-server"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: 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.). The author declared them in the registry entry; get the values from the project itself.