Azure IoT Hub

io.github.nagarjunr由 GitHub 账号 nagarjunr 发布v0.1.0更新于 Oct 24, 2026

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

已验证STDIO仅桌面数据库云端与基础设施

概览

AI 生成的概览

面向 Azure IoT Hub 设备管理的本地 MCP 服务器,让助手管理设备与模块、读写孪生、调用直接方法、运行作业并发送云到设备消息。

可以做什么
列出、查询、读取、创建、更新和删除设备标识,删除不可逆且需确认标志
运行要求
以 Python 包形式通过 uvx 在本地运行。需要在 AZURE_IOT_HUB_CONNECTION_STRING 中提供具有 service 或 iothubowner 权限的 Azure IoT Hub 连接字符串,并能访问该中心的网络。可选 AZURE_IOT_HUB_AMQP_PORT、AZURE_IOT_HUB_AMQP_USE_TLS 和 AZURE_IOT_HUB_AMQP_HOSTNAME_OVERRIDE 用于调整 AMQP 连接。
安装前请注意
连接字符串是授予中心服务级控制权的高权限密钥,勿放入共享配置。工具会创建、更新、删除设备、模块和孪生,并取消作业,改变真实设备群状态;删除与取消不可逆。直接方法和作业会作用于真实设备。云到设备发送未在真实中心验证,使用前应先测试。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Azure IoT Hub,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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.

来源:azure-iot-hub/README.md,提交 5a985b6

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.0最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分