Reads a boat's Signal K data and helps an AI assistant design and install KIP dashboards.
If you already use KIP, the kip mcp server is the piece that lets your assistant work with it directly. Reads a boat's Signal K data and helps an AI assistant design and install KIP dashboards.
You stay in control: the assistant shows you a picture of each dashboard first, and it only saves anything to your boat after you say yes.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
path — the name of one piece of data, like navigation.speedOverGround (speed overKIP — the app that shows your boat's data as dashboards of gauges and panelswidget — one gauge or panel on a dashboard (a number, a dial, a wind display, …)dashboard — a screen full of widgets, laid out on a gridtoken — like a password for software: it lets the server save changes to your boatSetting — What it isSIGNALK_HOST — Your Signal K host name or IPSIGNALK_PORT — Your Signal K portSIGNALK_TLS — Set to true if your server uses httpsSIGNALK_TOKEN — A Signal K login token, needed to write dashboardsSIGNALK_USER — A Signal K username — used with SIGNALK_PASSWORD instead of a tokenSIGNALK_PASSWORD — The matching Signal K passwordConfiguration is passed through the environment: SIGNALK_HOST, SIGNALK_TOKEN, MCP_BEARER_TOKEN, MCP_PUBLIC_URL, HTTP_HOST, HTTP_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at kip-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. KIP's toolset — path, KIP, widget and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dillan; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| path | the name of one piece of data, like navigation.speedOverGround (speed over |
| KIP | the app that shows your boat's data as dashboards of gauges and panels. |
| widget | one gauge or panel on a dashboard (a number, a dial, a wind display, …). |
| dashboard | a screen full of widgets, laid out on a grid. |
| token | like a password for software: it lets the server save changes to your boat. |
| Setting | What it is |
| SIGNALK_HOST | Your Signal K host name or IP |
| SIGNALK_PORT | Your Signal K port |
| SIGNALK_TLS | Set to true if your server uses https |
| SIGNALK_TOKEN | A Signal K login token, needed to **write** dashboards |
| SIGNALK_USER | A Signal K username — used with SIGNALK_PASSWORD instead of a token |
| SIGNALK_PASSWORD | The matching Signal K password |
| KIP_URL | Override where KIP is served, if it's not the default |
| HTTP_HOST | Address to bind |
{
"mcpServers": {
"kip": {
"command": "npx",
"args": ["-y", "kip-mcp-server"],
"env": {
"SIGNALK_HOST": "your-value",
"SIGNALK_TOKEN": "your-value",
"MCP_BEARER_TOKEN": "your-value",
"MCP_PUBLIC_URL": "your-value",
"HTTP_HOST": "your-value",
"HTTP_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SIGNALK_HOST | Endpoint or connection string the server talks to. | Optional |
| SIGNALK_TOKEN | Credential the server authenticates with. | Yes |
| MCP_BEARER_TOKEN | Credential the server authenticates with. | Yes |
| MCP_PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
| HTTP_HOST | Endpoint or connection string the server talks to. | Optional |
| HTTP_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.