Azure IoT Hub

io.github.nagarjunrPublished by GitHub account nagarjunrv0.1.0Updated Oct 24, 2026

MCP server for Azure IoT Hub: device registry, twins, methods, jobs, messaging.

VerifiedSTDIODesktop onlyDatabasesCloud & Infrastructure

Overview

AI-generated overview

Local MCP server for Azure IoT Hub device management: list, create, update and delete devices and modules, read and update twins, invoke direct methods, run and

What you can do
List, query, read, create, update and delete device identities, with irreversible deletes gated by a confirm flag
Requirements
Runs locally as a Python package via uvx. Requires an Azure IoT Hub connection string with service or iothubowner rights in AZURE_IOT_HUB_CONNECTION_STRING, plus network access to the hub. Optional AZURE_IOT_HUB_AMQP_PORT, AZURE_IOT_HUB_AMQP_USE_TLS and AZURE_IOT_HUB_AMQP_HOSTNAME_OVERRIDE tune the AMQP path.
Before you install
The connection string is a powerful secret granting service-level control of the hub; keep it out of shared configs. Tools create, update and delete devices, modules and twins, and cancel jobs, changing real fleet state; deletes and cancels are irreversible. Direct methods and jobs act on physical devices. Cloud-to-device sending is untested against a real hub and should be verified first.

Installation

In SourceWeft

  1. Open Azure IoT Hub in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Azure IoT Hub MCP Server

A Model Context Protocol (MCP) server for Azure IoT Hub — device registry, device twins, direct methods, jobs, and messaging.

Scoped to IoT Hub's service-side data plane (device management), not Azure Resource Manager. Microsoft's own official Azure MCP Server already covers the ARM-level "show me my IoT Hub resource" case — this server covers the actual device-management capability that Azure MCP doesn't.

Calls Azure IoT Hub's REST Service API directly via httpx with a hand-rolled SAS token generator, rather than the official azure-iot-hub PyPI package — that package hard-depends on uamqp, a C-extension that fails to build on modern Python/platforms (confirmed: it doesn't install on Python 3.12/arm64). Built with FastMCP.

Tools

Device registry

ToolDescription
list_devices(max_count)List devices. For filtering, prefer query_devices.
query_devices(query, max_item_count, continuation_token)IoT Hub SQL-like query over devices/twins, with pagination.
get_device(device_id)Fetch a device's identity (auth mechanism, status, connection state).
create_device(device_id, auth_type, ..., overwrite=False)Register a device.
update_device(device_id, status, status_reason, etag)Update a device's enabled/disabled status.
delete_device(device_id, confirm=False, etag)Delete a device. Irreversible.

Modules

ToolDescription
list_modules(device_id) / get_module(device_id, module_id)List/read module identities on a device.
create_module(device_id, module_id, ..., overwrite=False)Register a module.
delete_module(device_id, module_id, confirm=False)Delete a module. Irreversible.

Device & module twins

ToolDescription
get_device_twin(device_id) / get_module_twin(device_id, module_id)Read a twin (tags, desired/reported properties).
update_device_twin(device_id, tags, desired_properties, etag)Merge-update tags/desired properties.
replace_device_twin(device_id, tags, desired_properties, etag)Full replace (not merge) of tags/desired properties.
update_module_twin(device_id, module_id, tags, desired_properties, etag)Merge-update a module twin.

Direct methods

ToolDescription
invoke_device_method(device_id, method_name, payload, ...)Invoke a direct method on a device (blocks until the device responds or times out).
invoke_module_method(device_id, module_id, method_name, payload, ...)Same, scoped to a module.

Jobs (fleet-scale operations)

ToolDescription
create_scheduled_job(job_id, job_type, query_condition, ...)Schedule a twin update or direct method across many devices matching a query.
get_scheduled_job(job_id) / query_scheduled_jobs(job_type, job_status)Read job status/results.
cancel_scheduled_job(job_id, confirm=False)Cancel a job.

Messaging

ToolDescription
send_c2d_message(device_id, payload, ...)Send a cloud-to-device message. AMQP, not REST — see caveat below.
purge_c2d_message_queue(device_id)Delete all pending C2D messages queued for a device.

Statistics

ToolDescription
get_device_statistics()Total/enabled/disabled device counts.
get_service_statistics()Service-level stats (e.g. connected device count).

Important caveat: send_c2d_message is AMQP, not REST, and has no real-instance test coverage

Every other tool in this server wraps a documented REST endpoint. Cloud-to-device message sending is the one exception: Azure IoT Hub's REST API only exposes the feedback side of C2D messaging (delivery receipts); sending is AMQP-protocol-only (confirmed by reading the official azure-iot-hub SDK's source — it hands off to an AMQP client, not an HTTP call).

To support it without pulling in the broken uamqp dependency, send_c2d_message implements the CBS (Claims-Based Security) auth handshake and message send directly against python-qpid-proton (the standard AMQP 1.0 library, confirmed to install cleanly on modern Python). The protocol details (CBS field names, $cbs node, /messages/devicebound target address, to property format) were confirmed from Microsoft's own pure-Python AMQP implementation in azure-eventhub/azure-servicebus, not guessed.

This tool is not covered by real-instance testing. There's no free Azure IoT Hub emulator (see Testing below), and the test suite's respx HTTP mocking can't exercise AMQP at all. Tests instead run this against a local fake AMQP endpoint (also built with qpid-proton) that implements just enough of the CBS handshake and /messages/devicebound receiver to prove the wire protocol is well-formed — it does not validate genuine Azure IoT Hub business logic. Verify against a real hub before relying on this in production.

Safety conventions

Same as the rest of this repo: create_* defaults to overwrite=False (best-effort describe-then-create check — IoT Hub's If-Match header is for optimistic-concurrency on updates, not create-only semantics, so this isn't fully race-free like Ditto's If-None-Match). Every delete_*/cancel_* requires confirm=True.

Configuration

Env varRequiredDescription
AZURE_IOT_HUB_CONNECTION_STRINGYesAn IoT Hub connection string with service (or iothubowner) rights, e.g. HostName=my-hub.azure-devices.net;SharedAccessKeyName=service;SharedAccessKey=.... Find this under your hub's "Shared access policies" in the Azure portal.
AZURE_IOT_HUB_AMQP_PORTNoDefault 5671. Only relevant to send_c2d_message.
AZURE_IOT_HUB_AMQP_USE_TLSNotrue/false, default true. Set false only for local/test endpoints.
AZURE_IOT_HUB_AMQP_HOSTNAME_OVERRIDENoOverride the AMQP connection target (e.g. a local test fixture) without changing the REST hostname derived from the connection string.

Running locally

bash
uv syncexport AZURE_IOT_HUB_CONNECTION_STRING="HostName=my-hub.azure-devices.net;SharedAccessKeyName=service;SharedAccessKey=..."uv run azureiothubmcpserver.py

See mcp.json for ready-to-use client configs (stdio and Docker).

Testing

This repo's design principles call for testing against a real instance rather than mocks. Azure IoT Hub has no official local emulator and no moto-equivalent exists for it. REST endpoints are tested with respx (httpx's dedicated mocking library, using realistic Azure response shapes); send_c2d_message is tested against a local fake AMQP endpoint (see caveat above).

bash
uv run pytest -v

License notes

No bundled deployment artifacts here (unlike eclipse-ditto/mqtt) since there's no local broker/service to run — Azure IoT Hub only exists as an Azure-hosted service.

Source: azure-iot-hub/README.md at commit 5a985b6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts