Sparkplug B runs on your own machine — the client starts it, so there is no endpoint to ping. 96 installs a week from pypi. Last commit 31 Oct 2026.
MCP server for Sparkplug B: node/device discovery, metrics, commands, host state over MQTT.
We read the source, 7 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
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 sparkplug-b -e 'SPARKPLUG_MQTT_HOST=<SPARKPLUG_MQTT_HOST>' -e 'SPARKPLUG_HOST_ID=<SPARKPLUG_HOST_ID>' -- uvx sparkplug-b-mcp-server
{
"mcpServers": {
"sparkplug-b": {
"command": "uvx",
"args": [
"sparkplug-b-mcp-server"
],
"env": {
"SPARKPLUG_HOST_ID": "<SPARKPLUG_HOST_ID>",
"SPARKPLUG_MQTT_HOST": "<SPARKPLUG_MQTT_HOST>"
}
}
}
}
[mcp_servers.sparkplug-b]
command = "uvx"
args = ["sparkplug-b-mcp-server"]
env = { SPARKPLUG_MQTT_HOST = "<SPARKPLUG_MQTT_HOST>", SPARKPLUG_HOST_ID = "<SPARKPLUG_HOST_ID>" }
{
"mcpServers": {
"sparkplug-b": {
"command": "uvx",
"args": [
"sparkplug-b-mcp-server"
],
"env": {
"SPARKPLUG_HOST_ID": "<SPARKPLUG_HOST_ID>",
"SPARKPLUG_MQTT_HOST": "<SPARKPLUG_MQTT_HOST>"
}
}
}
}
{
"servers": {
"sparkplug-b": {
"type": "stdio",
"command": "uvx",
"args": [
"sparkplug-b-mcp-server"
],
"env": {
"SPARKPLUG_HOST_ID": "<SPARKPLUG_HOST_ID>",
"SPARKPLUG_MQTT_HOST": "<SPARKPLUG_MQTT_HOST>"
}
}
}
}
Put your own values in place of
<SPARKPLUG_MQTT_HOST> (MQTT broker hostname or IP), <SPARKPLUG_HOST_ID> (This connector's Sparkplug Host Application ID (used in the spBv1.0/STATE/{id} topic)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
SPARKPLUG_MQTT_PORT (MQTT broker port, default 1883), SPARKPLUG_MQTT_USERNAME (Broker username, if required), SPARKPLUG_MQTT_PASSWORD (Broker password, if required), SPARKPLUG_MQTT_USE_TLS (true/false, default false), SPARKPLUG_GROUP_ID (Restrict discovery/watching to a single Sparkplug Group ID; omit to subscribe to every group).
MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.
MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.
MCP Server for vmanomaly - VictoriaMetrics anomaly detection
MCP Server for vmanomaly - VictoriaMetrics anomaly detection
MCP server for Duplicacy: backup health, status and Prometheus metrics from duplicacy-exporter
MCP server for Yandex.Metrica Stat API (read-only).
A community MCP server for the Discord REST API with traceable coverage
MCP server for Google Lighthouse performance metrics
Answers built from our own checks of this server.