KIP MCP Server

Name: KIP MCP Server
Author: dillan

作者：dillan版本 1.12.0i★ –i在你的电脑上运行

注册名称io.github.dillan/kip-mcp-server

安装

概览

作者提供的说明（英文原文）

Reads a boat's Signal K data and helps an AI assistant design and install KIP dashboards.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 设计、图片与音频
你需要填写：SIGNALK_TOKEN, SIGNALK_PASSWORD

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： SIGNALK_HOST, SIGNALK_PORT, SIGNALK_TLS, SIGNALK_TOKEN, SIGNALK_USER, SIGNALK_PASSWORD, KIP_URL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "kip": {
      "command": "npx",
      "args": [
        "-y",
        "kip-mcp-server"
      ],
      "env": {
        "SIGNALK_HOST": "your-value",
        "SIGNALK_PORT": "your-value",
        "SIGNALK_TLS": "your-value",
        "SIGNALK_TOKEN": "your-value",
        "SIGNALK_USER": "your-value",
        "SIGNALK_PASSWORD": "your-value",
        "KIP_URL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add kip --env SIGNALK_HOST=your-value --env SIGNALK_PORT=your-value --env SIGNALK_TLS=your-value --env SIGNALK_TOKEN=your-value --env SIGNALK_USER=your-value --env SIGNALK_PASSWORD=your-value --env KIP_URL=your-value -- npx -y kip-mcp-server

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "kip": {
      "command": "npx",
      "args": [
        "-y",
        "kip-mcp-server"
      ],
      "env": {
        "SIGNALK_HOST": "your-value",
        "SIGNALK_PORT": "your-value",
        "SIGNALK_TLS": "your-value",
        "SIGNALK_TOKEN": "your-value",
        "SIGNALK_USER": "your-value",
        "SIGNALK_PASSWORD": "your-value",
        "KIP_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "kip": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "kip-mcp-server"
      ],
      "env": {
        "SIGNALK_HOST": "your-value",
        "SIGNALK_PORT": "your-value",
        "SIGNALK_TLS": "your-value",
        "SIGNALK_TOKEN": "your-value",
        "SIGNALK_USER": "your-value",
        "SIGNALK_PASSWORD": "your-value",
        "KIP_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

SIGNALK_HOST env
Signal K server host name or IP.
SIGNALK_PORT env
Signal K server port.
SIGNALK_TLS env
Set true if Signal K uses https/wss.
SIGNALK_TOKEN 机密 env
Signal K token, needed to write dashboards (or use SIGNALK_USER/PASSWORD).
SIGNALK_USER env
Signal K username, used with SIGNALK_PASSWORD instead of a token.
SIGNALK_PASSWORD 机密 env
Signal K password, used with SIGNALK_USER.
KIP_URL env
Override where KIP is served, if it is not the default.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 dillan 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“设计、图片与音频”中的其他服务器比较i

星标数多于此分类中其他 2204 个服务器的 0%
发布到注册中心的时间比此分类中其他 2204 个服务器的 13% 更新
基础检查结果等于或优于此分类中其他 2204 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

KIP MCP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：SIGNALK_TOKEN, SIGNALK_PASSWORD

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.12.0）于5个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Figma Context MCP, Claude Real Video, Figma MCP Server

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Figma Context MCP

作者：GLips

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

在你的电脑上运行★ 16,165MIT5个月前更新

安装

Claude Real Video

作者：HUANGCHIHHUNGLeo

Let any LLM watch a video locally — and search everything it has ever watched.

在你的电脑上运行★ 2,284MIT2个月前更新

安装

Figma MCP Server

作者：figma

The Figma MCP server brings Figma design context directly into your AI workflow.

在云端运行★ 2,15213个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

kip-mcp-server

An MCP server that lets an AI assistant (such as Claude, Codex, or Gemini) look at your boat's Signal K data and help you design and install KIP dashboards — the gauges and panels you see on your chartplotter or tablet.

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.

What it does

Looks at your boat's data. It finds the values your boat reports through Signal K — speed, wind, depth, batteries, engine, and so on.
Suggests dashboards. It proposes a general dashboard plus ones for specific jobs: sailing, motoring, power, anchoring, navigation, and weather.
Shows you a preview. You see a simple picture of each dashboard before anything is saved.
Installs them — with your OK. It writes the dashboards to your KIP setup, or hands you a file you can import yourself.

What it looks like

A short session with an AI assistant, after pointing it at your boat:

You:  Look at my boat's data and suggest some KIP dashboards.

→ analyze_signalk_data 142 paths · speed, wind, depth, battery, engine → recommend_dashboard_set 6 dashboards the data supports

Assistant: Your boat reports navigation, wind, depth, electrical and engine data, so I can build these. Here's the "Sailing" one — a preview, nothing saved yet:

┌─────────────┬─────────────┬───────────────────────────┐ │ SOG 6.2 kn │ AWS 14 kn │ │ ├─────────────┼─────────────┤ wind steering │ │ DPT 8.4 m │ AWA 42° │ │ └─────────────┴─────────────┴───────────────────────────┘

You: Looks good — install the sailing and anchor ones.

→ apply_kip_config (dry run) 2 dashboards → KipConfig (global) Assistant: This will add "Sailing" and "Anchor" to KIP. Go ahead? You: Yes. → apply_kip_config written ✓ — open KIP to see them.

The assistant always shows a preview first and asks before writing anything to your boat.

Quick start (for boat owners)

You need a Signal K server running on your boat (or on your network), with KIP installed.

Find your Signal K address. It usually looks like http://your-boat:3000. Note the host name (or IP) and port.
Get this server. You don't need to install anything by hand — your AI assistant can run it on demand with npx (which comes with Node.js 24 or newer):

   npx -y kip-mcp-server

The next step wires this command into your assistant. (Prefer to build from source? See Develop below.)

Connect it to your AI assistant. Pick your assistant in docs/clients and follow the short setup there. You tell the assistant your boat's host and port.
Ask it to help. Say something like *"Look at my boat's data and suggest some KIP dashboards."* Review the previews it shows you.
Say yes. When you're happy, tell it to go ahead. It asks before writing anything. If your Signal K server is older, it gives you a KipConfig.json file to import from KIP's Settings instead.

How to connect it

The server reads a few settings from its environment:

Setting	What it is	Default
`SIGNALK_HOST`	Your Signal K host name or IP	`localhost`
`SIGNALK_PORT`	Your Signal K port	`3000`
`SIGNALK_TLS`	Set to `true` if your server uses `https`	`false`
`SIGNALK_TOKEN`	A Signal K login token, needed to write dashboards	(none)
`SIGNALK_USER`	A Signal K username — used with `SIGNALK_PASSWORD` instead of a token	(none)
`SIGNALK_PASSWORD`	The matching Signal K password	(none)
`KIP_URL`	Override where KIP is served, if it's not the default	(derived)

Reading your data needs no login. Writing dashboards to the server needs either a token or a username and password; you can always use the file-export option instead, which needs nothing extra. For how to get a token (or why a username/password is simpler), see Signal K authentication.

Remote access over HTTP (optional, advanced)

By default the server talks over stdio — the assistant runs it as a local subprocess. There is also an optional HTTP mode (kip-mcp-http) for hosting the server so a remote assistant (such as Claude.ai) can reach it over the network. It is opt-in and meant for a single operator behind a reverse proxy that adds TLS.

# Behind a TLS-terminating reverse proxy that forwards to 127.0.0.1:3017

MCP_BEARER_TOKEN=a-long-random-secret \ MCP_PUBLIC_URL=https://boat.example.com/mcp \ npx kip-mcp-http

Setting	What it is	Default
`HTTP_HOST`	Address to bind	`127.0.0.1` (loopback)
`HTTP_PORT`	Port to listen on	`3017`
`HTTP_PATH`	URL path for the MCP endpoint	`/mcp`
`MCP_BEARER_TOKEN`	One or more (comma-separated) bearer tokens that callers must present	(none)
`MCP_PUBLIC_URL`	The public URL clients reach, used for the Host allowlist and metadata	(derived)
`MCP_ALLOWED_ORIGINS`	Comma-separated browser origins to accept (off by default)	(none)
`MCP_ALLOWED_HOSTS`	Override the Host allowlist	(derived)
`MCP_ALLOW_INSECURE`	Set to `true` to start anyway in an unsafe setup	(unset)

Every request must present a valid Authorization: Bearer and pass a Host/Origin allowlist before it reaches the MCP layer. The server refuses to start if it would bind to a non-loopback address or run without a bearer token, unless you set MCP_ALLOW_INSECURE=true. It uses one Signal K login for all sessions, so treat it as a single-tenant deployment; the same SIGNALK_* settings above apply.

What the assistant can do

The server gives the assistant a set of tools, grouped by job:

Look at the boat — list the data paths, their units, and which plugins are installed.
Know KIP's parts — list every KIP widget and how it's configured, plus the colours, icons and units KIP understands.
Design dashboards — suggest a set of dashboards, build one for a chosen job, and draw a preview.
Review the UX — critique a dashboard for marine usability (hierarchy, grouping, consistency, labels) with severity-tagged findings; the review_dashboard prompt drives it, backed by a deterministic check_dashboard_ux lint.
Check and save — check a dashboard is well-formed, export it to a file, or write it to the boat (asking first).

More help

[Recipes](./docs/recipes.md) — worked examples of asking the assistant to design dashboards.
[Troubleshooting](./docs/troubleshooting.md) — fixes for the common problems, starting with the built-in --doctor check.
[Tool reference](./docs/tools.md) — every tool and prompt the assistant can use.

Glossary

A few terms, in plain words:

Signal K — the open system many boats use to share data (speed, wind, depth, …) over the network.
path — the name of one piece of data, like navigation.speedOverGround (speed over ground).
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.
dry run — the assistant tells you what it *would* do, without actually doing it. Saving is a dry run by default.

Develop

This project uses Node.js 24 (LTS). Common commands:

npm install        # install dependencies

npm run typecheck # check types npm run lint # check code style npm test # run the tests npm run build # compile to dist/ npm run smoke # start the built server and check it answers npm run ci # run the full set of checks

For a full guide to running and testing the server locally during development — pointing an AI client or the MCP Inspector at a local build, running the HTTP transport, and testing against Signal K (or offline) — see docs/development.md.

Commits follow Conventional Commits; releases and version numbers are produced automatically from those commit messages.

License

MIT — see LICENSE.