Azure IoT Hub vs Eclipse Ditto
Azure IoT Hub is an MCP server published by nagarjunr. Marketplaces we read that list it: 1 (Official MCP Registry). Eclipse Ditto is an MCP server published by nagarjunr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Azure IoT Hub | Eclipse Ditto |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (PyPI): 86 Downloads/week (PyPI): 25 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (PyPI): 85 Downloads/week (PyPI): 23 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Azure IoT Hub | Eclipse Ditto |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (azure-iot-hub-mcp-server) | On your machine (eclipse-ditto-mcp-server) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 6, secrets among them: 3 |
| Licence | Not stated | Not stated |
| Repository | github.com/nagarjunr/iot-mcp-servers | github.com/nagarjunr/iot-mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Azure IoT Hub
MCP server for Azure IoT Hub: device registry, twins, methods, jobs, messaging.
Eclipse Ditto
MCP server for the Eclipse Ditto digital twin HTTP API (things, policies, connections, more).
How to run each
Azure IoT Hub As a local MCP server: PyPI package
claude mcp add --env "AZURE_IOT_HUB_CONNECTION_STRING=<YOUR_AZURE_IOT_HUB_CONNECTION_STRING>" --transport stdio azure-iot-hub -- uvx azure-iot-hub-mcp-serverRequires: AZURE_IOT_HUB_CONNECTION_STRING (secret)
Eclipse Ditto As a local MCP server: PyPI package
claude mcp add --env "DITTO_BASE_URL=<YOUR_DITTO_BASE_URL>" --env "DITTO_BEARER_TOKEN=<YOUR_DITTO_BEARER_TOKEN>" --env "DITTO_DEVOPS_PASSWORD=<YOUR_DITTO_DEVOPS_PASSWORD>" --env "DITTO_PASSWORD=<YOUR_DITTO_PASSWORD>" --transport stdio eclipse-ditto -- uvx eclipse-ditto-mcp-serverRequires: DITTO_BASE_URL, DITTO_BEARER_TOKEN (secret), DITTO_DEVOPS_PASSWORD (secret), DITTO_PASSWORD (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Azure IoT Hub asks for
AZURE_IOT_HUB_AMQP_PORTAZURE_IOT_HUB_AMQP_USE_TLSAZURE_IOT_HUB_CONNECTION_STRING (secret)
Only Eclipse Ditto asks for
DITTO_BASE_URLDITTO_BEARER_TOKEN (secret)DITTO_DEVOPS_PASSWORD (secret)DITTO_DEVOPS_USERNAMEDITTO_PASSWORD (secret)DITTO_USERNAME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Azure IoT Hub · What it can do: Eclipse Ditto · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.