mcpField
S
Sparkplug B

Sparkplug B

Local
github.com/nagarjunrDeveloper Tools0Updated 1w ago

About Sparkplug B

Sparkplug B is an MCP server for industrial and SCADA data workflows. It discovers MQTT-connected nodes and devices, tracks metrics, and supports commands and event monitoring.

Key features

  1. 01Discover Edge Nodes and Devices
  2. 02Read node and device metrics
  3. 03Send node and device commands
  4. 04Watch filtered Sparkplug traffic
  5. 05Track host connection state

Use cases

  1. 01Inspect live metrics from industrial devices
  2. 02Issue commands to nodes or devices
  3. 03Monitor selected Sparkplug message events

MCP support

Exposes Sparkplug B discovery, metrics, commands, host state, and event-watch operations as tools for MCP clients. It connects to an MQTT broker carrying Sparkplug B traffic.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"nagarjunr-sparkplug-b": {
"command": "uvx",
"args": [
"sparkplug-b-mcp-server"
],
"env": {
"SPARKPLUG_MQTT_HOST": "<SPARKPLUG_MQTT_HOST>",
"SPARKPLUG_HOST_ID": "<SPARKPLUG_HOST_ID>",
"SPARKPLUG_MQTT_PORT": "<SPARKPLUG_MQTT_PORT>",
"SPARKPLUG_MQTT_USERNAME": "<SPARKPLUG_MQTT_USERNAME>",
"SPARKPLUG_MQTT_PASSWORD": "<SPARKPLUG_MQTT_PASSWORD>",
"SPARKPLUG_MQTT_USE_TLS": "<SPARKPLUG_MQTT_USE_TLS>",
"SPARKPLUG_GROUP_ID": "<SPARKPLUG_GROUP_ID>"
}
}
}
}
Run commanduvx sparkplug-b-mcp-server
Environment variables to set
SPARKPLUG_MQTT_HOSTMQTT broker hostname or IP.
SPARKPLUG_HOST_IDThis connector's Sparkplug Host Application ID (used in the spBv1.0/STATE/{id} topic).
SPARKPLUG_MQTT_PORTMQTT broker port, default 1883
SPARKPLUG_MQTT_USERNAMEBroker username, if required
SPARKPLUG_MQTT_PASSWORDSecretBroker password, if required
SPARKPLUG_MQTT_USE_TLStrue/false, default false
SPARKPLUG_GROUP_IDRestrict discovery/watching to a single Sparkplug Group ID; omit to subscribe to every group

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypisparkplug-b-mcp-server0.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Sparkplug B MCP Server

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).

Tools

ToolDescription
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.
Why watching is session-based

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.

Supported metric datatypes

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.

Configuration

Env varRequiredDescription
SPARKPLUG_MQTT_HOSTYesBroker hostname or IP.
SPARKPLUG_HOST_IDYesThis connector's Sparkplug Host Application ID (used in the spBv1.0/STATE/{id} topic).
SPARKPLUG_MQTT_PORTNoDefault 1883.
SPARKPLUG_MQTT_USERNAME / SPARKPLUG_MQTT_PASSWORDNoBroker credentials.
SPARKPLUG_MQTT_CLIENT_IDNoDefaults to a broker-assigned ID.
SPARKPLUG_MQTT_KEEPALIVENoSeconds, default 60.
SPARKPLUG_MQTT_CONNECT_TIMEOUTNoSeconds to wait for the initial connect, default 10.
SPARKPLUG_MQTT_USE_TLSNotrue/false, default false.
SPARKPLUG_MQTT_TLS_CA_CERTSNoPath to a CA bundle. Omit to use the system trust store.
SPARKPLUG_MQTT_TLS_CLIENT_CERT / SPARKPLUG_MQTT_TLS_CLIENT_KEYNoFor mutual TLS.
SPARKPLUG_GROUP_IDNoRestrict discovery/watching to a single Sparkplug Group ID. Omit to subscribe to every group (spBv1.0/#).

Running locally

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).

Testing against a real broker

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

License notes

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.