Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP server for Sparkplug B: node/device discovery, metrics, commands, host state over MQTT.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
SPARKPLUG_MQTT_HOST, SPARKPLUG_HOST_ID, SPARKPLUG_MQTT_PORT, SPARKPLUG_MQTT_USERNAME, SPARKPLUG_MQTT_PASSWORD, SPARKPLUG_MQTT_USE_TLS, SPARKPLUG_GROUP_ID标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"sparkplug-b": {
"command": "uvx",
"args": [
"sparkplug-b-mcp-server"
],
"env": {
"SPARKPLUG_MQTT_HOST": "your-value",
"SPARKPLUG_HOST_ID": "your-value",
"SPARKPLUG_MQTT_PORT": "your-value",
"SPARKPLUG_MQTT_USERNAME": "your-value",
"SPARKPLUG_MQTT_PASSWORD": "your-value",
"SPARKPLUG_MQTT_USE_TLS": "your-value",
"SPARKPLUG_GROUP_ID": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add sparkplug-b --env SPARKPLUG_MQTT_HOST=your-value --env SPARKPLUG_HOST_ID=your-value --env SPARKPLUG_MQTT_PORT=your-value --env SPARKPLUG_MQTT_USERNAME=your-value --env SPARKPLUG_MQTT_PASSWORD=your-value --env SPARKPLUG_MQTT_USE_TLS=your-value --env SPARKPLUG_GROUP_ID=your-value -- uvx sparkplug-b-mcp-server运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"sparkplug-b": {
"command": "uvx",
"args": [
"sparkplug-b-mcp-server"
],
"env": {
"SPARKPLUG_MQTT_HOST": "your-value",
"SPARKPLUG_HOST_ID": "your-value",
"SPARKPLUG_MQTT_PORT": "your-value",
"SPARKPLUG_MQTT_USERNAME": "your-value",
"SPARKPLUG_MQTT_PASSWORD": "your-value",
"SPARKPLUG_MQTT_USE_TLS": "your-value",
"SPARKPLUG_GROUP_ID": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"sparkplug-b": {
"type": "stdio",
"command": "uvx",
"args": [
"sparkplug-b-mcp-server"
],
"env": {
"SPARKPLUG_MQTT_HOST": "your-value",
"SPARKPLUG_HOST_ID": "your-value",
"SPARKPLUG_MQTT_PORT": "your-value",
"SPARKPLUG_MQTT_USERNAME": "your-value",
"SPARKPLUG_MQTT_PASSWORD": "your-value",
"SPARKPLUG_MQTT_USE_TLS": "your-value",
"SPARKPLUG_GROUP_ID": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
SPARKPLUG_MQTT_PORT envSPARKPLUG_MQTT_USERNAME envSPARKPLUG_MQTT_USE_TLS envSPARKPLUG_GROUP_ID env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日
注册名称已通过 GitHub 账户 nagarjunr 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:SPARKPLUG_MQTT_HOST, SPARKPLUG_HOST_ID, SPARKPLUG_MQTT_PASSWORD
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, agentPickup
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find pickup shops near you, order, pay by card or USDC (x402), and get the QR to collect in person.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A Model Context Protocol (MCP) server for Sparkplug B — the Eclipse-standard MQTT topic/payload convention for industrial/SCADA data (birth/death certificates, sequenced metrics, protobuf payloads). Works against any MQTT broker that carries Sparkplug B traffic; only the open Sparkplug B specification is used, no vendor-specific extensions.
This server acts as a Sparkplug B Primary Host Application: it subscribes to the entire spBv1.0 namespace, discovers Edge Nodes and Devices from their NBIRTH/DBIRTH messages, tracks their live metrics, and can send them commands (NCMD/DCMD) — the same role a SCADA/historian host application plays in a real deployment.
Built with FastMCP and pysparkplug (itself built on paho-mqtt).
| Tool | Description |
|---|---|
get_connection_status() | Report the broker connection and this host application's identity. |
set_host_online(online) | Publish this connector's own retained Sparkplug STATE message. |
list_edge_nodes(group_id?) | List Edge Nodes discovered via NBIRTH/NDEATH. |
list_devices(group_id?, edge_node_id?) | List Devices discovered via DBIRTH/DDEATH. |
get_node_metrics(group_id, edge_node_id) | Latest known metric values for an Edge Node. |
get_device_metrics(group_id, edge_node_id, device_id) | Latest known metric values for a Device. |
send_node_command(group_id, edge_node_id, metrics) | Send an NCMD — write one or more of a node's metrics. |
send_device_command(group_id, edge_node_id, device_id, metrics) | Send a DCMD — write one or more of a device's metrics. |
request_node_rebirth(group_id, edge_node_id) | Standard Node Control/Rebirth command — asks a node to republish its full NBIRTH. |
start_watch(group_id?, edge_node_id?, device_id?, message_types?) | Start buffering decoded Sparkplug traffic matching an optional filter. Returns a session_id. |
get_events(session_id, max_events, timeout_seconds) | Drain buffered events from a watch session; can wait briefly for one to arrive. |
stop_watch(session_id) | Stop a watch session and discard its buffered events. |
list_watches() | List all active watch sessions. |
Like the MQTT wire protocol underneath it, Sparkplug B is a continuous stream, not a request/response API — a single MCP tool call can't "wait forever" for the next birth or data message. start_watch registers an optional filter (group/node/device/message-type) and buffers matching decoded messages in the background (this connector is always subscribed to the whole spBv1.0 namespace, so no extra broker subscription is needed per watch); get_events drains that buffer, optionally waiting a bounded amount of time for new data. Call stop_watch when done.
INT8/INT16/INT32/INT64, UINT8/UINT16/UINT32/UINT64, FLOAT, DOUBLE, BOOLEAN, STRING, TEXT, UUID, DATETIME, BYTES, FILE, and their *_ARRAY variants. DATASET, TEMPLATE, PROPERTYSET, and PROPERTYSETLIST are part of the Sparkplug B spec but unsupported by the underlying pysparkplug codec, so they're rejected with a clear error rather than silently mishandled.
For send_node_command/send_device_command, value shape depends on datatype: plain int/float/bool/str for scalars, an ISO 8601 string for DATETIME, a base64 string for BYTES/FILE, and a JSON list for *_ARRAY types.
| Env var | Required | Description |
|---|---|---|
SPARKPLUG_MQTT_HOST | Yes | Broker hostname or IP. |
SPARKPLUG_HOST_ID | Yes | This connector's Sparkplug Host Application ID (used in the spBv1.0/STATE/{id} topic). |
SPARKPLUG_MQTT_PORT | No | Default 1883. |
SPARKPLUG_MQTT_USERNAME / SPARKPLUG_MQTT_PASSWORD | No | Broker credentials. |
SPARKPLUG_MQTT_CLIENT_ID | No | Defaults to a broker-assigned ID. |
SPARKPLUG_MQTT_KEEPALIVE | No | Seconds, default 60. |
SPARKPLUG_MQTT_CONNECT_TIMEOUT | No | Seconds to wait for the initial connect, default 10. |
SPARKPLUG_MQTT_USE_TLS | No | true/false, default false. |
SPARKPLUG_MQTT_TLS_CA_CERTS | No | Path to a CA bundle. Omit to use the system trust store. |
SPARKPLUG_MQTT_TLS_CLIENT_CERT / SPARKPLUG_MQTT_TLS_CLIENT_KEY | No | For mutual TLS. |
SPARKPLUG_GROUP_ID | No | Restrict discovery/watching to a single Sparkplug Group ID. Omit to subscribe to every group (spBv1.0/#). |
uv sync
export SPARKPLUG_MQTT_HOST=localhost export SPARKPLUG_MQTT_PORT=1883 export SPARKPLUG_HOST_ID=my-mcp-host uv run sparkplugbmcpserver.py
See mcp.json for ready-to-use client configs (stdio and Docker).
This repo's design principles call for testing against a real instance rather than mocks. docker-compose.yml spins up Eclipse Mosquitto (2.x) with an anonymous listener for local testing. Test fixtures use pysparkplug's own EdgeNode/Device classes to act as real simulated PLCs/devices — publishing genuine NBIRTH/DBIRTH/NDATA/DDATA/NDEATH messages and receiving genuine NCMD/DCMD commands over the wire — so coverage is protocol-level, not hand-rolled mocks. Only the "physical" node/device is simulated, since no free real PLC/edge-node hardware exists to test against; the Sparkplug B protocol handling on both sides is real.
docker compose up -d # start Mosquitto on localhost:1883 (anonymous, local testing only)
uv run pytest -v # tests/conftest.py also starts/stops the stack automatically docker compose down # stop it manually if you started it yourself
docker-compose.yml and the files under docker/ configure the open-source Eclipse Mosquitto broker (EPL-2.0) for local testing only — they are not part of the MCP server itself.