MCP.Market

Sparkplug B MCP server

by nagarjunr·io.github.nagarjunr/sparkplug-b·v0.1.0
No reviews yet

MCP server for Sparkplug B: node/device discovery, metrics, commands, host state over MQTT.

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars12 downloads/wk

Reviews

Write one

Nobody has reviewed Sparkplug B yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Sparkplug B tools (13, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_connection_status

    Report this connector's connection to the MQTT broker and its Sparkplug Host Application identity.

  • get_device_metrics

    Get the latest known metric values for a Device (from its DBIRTH/DDATA messages).

  • get_events

    Drain buffered Sparkplug events collected by a watch session.

  • get_node_metrics

    Get the latest known metric values for an Edge Node (from its NBIRTH/NDATA messages).

  • list_devices

    List Sparkplug Devices discovered via DBIRTH/DDEATH messages since this connector started.

  • list_edge_nodes

    List Sparkplug Edge Nodes discovered via NBIRTH/NDEATH messages since this connector started.

  • list_watches

    List all active watch sessions on this connector.

  • request_node_rebirth

    Ask an Edge Node to republish its full NBIRTH (the standard 'Node Control/Rebirth' command).

  • send_device_commandwrite action

    Send a DCMD to a Sparkplug Device to write one or more of its metrics.

  • send_node_commandwrite action

    Send an NCMD to a Sparkplug Edge Node to write one or more of its metrics.

  • set_host_onlinewrite action

    Publish this connector's own Sparkplug Host Application STATE message.

  • start_watch

    Start watching Sparkplug B traffic (births, deaths, data, commands, host states).

  • stop_watch

    Stop a watch session and discard its buffered events.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 50 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Sparkplug B compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,273 servers
Tools
13
the typical server has 7
Tools that change things
23%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
12
more than 3% of 11,915 servers with a package

What its tools let an agent do: 8 read · 1 change · 2 send or post · 2 run or deploy

Install Sparkplug B in Claude Code, Cursor or VS Code

claude mcp add sparkplug-b -- uvx sparkplug-b-mcp-server
Add to Cursor

What the publisher says

From the Sparkplug B repository's README, as published. We do not edit it. Read it on GitHub

IoT MCP Servers

MCP (Model Context Protocol) servers for IoT platforms — giving AI agents full read/write access to device registries, digital twins, and telemetry.

Servers

Each row links to that server's README for its full tool list, required environment variables, and setup/testing notes.

Structure

Each server is a standalone directory under this repo — its own pyproject.toml, uv.lock, Dockerfile, and mcp.json example config. No shared library layer: every server is independently runnable and dockerizable.

<server-name>/
├── <server-name>mcpserver.py   # FastMCP server (single file)
├── pyproject.toml              # own dependencies
├── uv.lock
├── Dockerfile
├── mcp.json                    # example MCP client config
└── README.md                   # tools, env vars, setup for this server

Requirements

  • Python 3.12+
  • uv for dependency management and running servers
  • Docker, only if you want to run a server's own test suite against a real/emulated instance (see that server's README)

Quick start

Install straight from PyPI with uv or pipx — no clone needed:

uvx eclipse-ditto-mcp-server      # or: mqtt5-mcp-server / aws-iot-core-mcp-server / azure-iot-hub-mcp-server / sparkplug-b-mcp-server

Or run from a clone of this repo:

git clone https://github.com/nagarjunr/iot-mcp-servers.git
cd iot-mcp-servers/<server-name>
uv sync
uv run <server-name>mcpserver.py

Each server reads its configuration from environment variables (connection strings, broker host, credentials, etc.) — see that server's README for the full list.

Using with an MCP client

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Sparkplug B: common questions

Is Sparkplug B MCP server safe?
Mostly: it is graded B (78/100). Read the Sparkplug B safety report
How do I install Sparkplug B?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Sparkplug B need an API key?
Yes. The registry entry asks for SPARKPLUG_MQTT_PASSWORD.
Is Sparkplug B maintained?
The last commit was 90 days ago (2026-08-04). The latest release is v0.1.0.
How does Sparkplug B compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,273 servers); tools 13 (the typical server has 7); tools that change things 23% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from nagarjunr →