MCP servers for IoT: AWS IoT Core, SiteWise, Azure IoT Hub and MQTT

Updated 3 November 2026

AWS does not publish an MCP server dedicated to AWS IoT Core: an AI agent reaches IoT Core through the general AWS MCP Server, generally available since 6 May 2026, while AWS IoT SiteWise has its own open-source MCP server with 73 tools. On the Microsoft side, the Azure MCP Server includes Azure IoT Hub tools, all read-only. This guide lists the MCP servers that exist for IoT platforms and MQTT brokers on 3 November 2026, what each one can change, and how to keep an agent read-only. Every row comes from the publisher’s own documentation, repository or package registry.

Key takeaways

• AWS IoT Core: use the AWS MCP Server. It is managed by AWS, has no additional charge and acts with your IAM permissions; read-only mode is a setting of the local MCP Proxy for AWS.
• AWS IoT SiteWise has a dedicated server: 73 tools for assets, models and industrial data, read-only unless you enable writes.
• Azure IoT Hub is covered by the Azure MCP Server, version 3.0.0: devices, device twins, queries and routing health, all read-only. Its documentation lists no tool for the Event Grid MQTT broker.
• MQTT: EMQX publishes an MCP server for EMQX Cloud and an “MCP over MQTT” transport; we found no official HiveMQ or Mosquitto MCP server.
• The data is free to reuse: download the list as CSV.

The servers at a glance

AWS IoT Core: use the AWS MCP Server

AWS keeps its open-source MCP servers in the awslabs/mcp repository. On 3 November 2026 it holds no server for AWS IoT Core; the only IoT server there is the SiteWise one. For IoT Core, AWS offers the AWS MCP Server, a remote server that AWS runs for you and that lets coding agents “interact with any AWS service”, according to its general availability announcement of 6 May 2026.

• How it reaches IoT Core. Its aws___run_script tool runs Python in a sandbox with AWS API access, so an agent can call the IoT Core APIs, for example to list things, within the IAM permissions you give it.
• Price. No additional charge; you pay for the AWS resources your agents use.
• Authentication. Either OAuth directly, or SigV4 signing through the local MCP Proxy for AWS.
• Read-only mode exists only on the SigV4 path: start the proxy with --read-only and the tools that may write are hidden from the agent.
• Regions. The getting-started guide lists eight endpoints, including Frankfurt (eu-central-1), Ireland (eu-west-1) and London (eu-west-2).

Adding it to Claude Code, from the getting-started guide:

claude mcp add aws-mcp https://aws-mcp.us-east-1.api.aws/mcp --transport http

Two older routes still appear in search results:

• The AWS API MCP Server runs AWS CLI commands, so it also reaches IoT Core, with READ_OPERATIONS_ONLY=true for read-only use and REQUIRE_MUTATION_CONSENT=true to ask before each change. Its own page now says it is superseded by the AWS MCP Server and intended for development, testing and evaluation.
• An AWS code sample, sample-MCP_server-for-Amazon_IoT_Core, exposes a single tool, publish_mqtt, that publishes a message to IoT Core. It is a sample, not a supported product; its last update dates from 20 September 2025.

The README of awslabs/mcp still labels the AWS MCP Server “in preview” on 3 November 2026; the AWS announcement of general availability is the more recent source.

AWS IoT SiteWise: a dedicated server

AWS announced an MCP server for AWS IoT SiteWise on 19 September 2025. Its README lists 73 tools, from asset and model management to queries (execute_query) and data ingestion (batch_put_asset_property_value).

• Read-only by default. Write tools are turned on only with the environment variable SITEWISE_MCP_ALLOW_WRITES=True.
• Runs locally (stdio) and installs with uvx awslabs.aws-iot-sitewise-mcp-server@latest.
• Version 11.0.23, published on PyPI on 8 September 2026.

Azure IoT Hub: the Azure MCP Server

Microsoft’s Azure MCP Server covers many Azure services in one server. Its command reference lists, on 3 November 2026:

• What it does not do. No IoT Hub tool creates or deletes devices, calls a direct method or sends a cloud-to-device message. The README, the command reference and the changelog do not mention MQTT, so the Event Grid MQTT broker has no tools.
• Read-only mode: start it with --read-only.
• Authentication uses your Azure credentials or a managed identity, with Azure role-based access control (RBAC).
• Runs locally (stdio) by default; it can also be hosted as a remote HTTP endpoint, for example on Azure Container Apps.
• Pin the version. The usual command is npx -y @azure/mcp@latest server start, but on 3 November 2026 the npm latest tag points to 4.0.0-beta.4, a beta; the last stable version is 3.0.0, published on 12 October 2026. Use @azure/mcp@3.0.0 for a stable install.

Microsoft Learn documents fewer IoT Hub tools than the repository: its IoT Hub page describes two. The command reference in the repository is the more complete source.

MQTT brokers and IoT data platforms

We found no official MCP server from HiveMQ or Eclipse Mosquitto: on 3 November 2026, the GitHub organisations hivemq, eclipse-mosquitto and cedalo hold no MCP project. Generic MQTT servers exist from individual developers (see below).

MCP over MQTT

MCP normally runs over stdio or HTTP. EMQX also publishes MCP over MQTT, which carries MCP messages on an MQTT broker, with SDKs for Erlang, ESP32 C, C (Paho), Python, TypeScript and Kotlin. Two AWS blog posts describe the same idea with AWS IoT Core as the broker: the AWS Germany blog on 9 April 2026 and the AWS Physical AI blog on 21 May 2026, where a robot talks MQTT and an AWS Lambda function translates for the agent. These are architectures, not products.

Community servers: check before you trust them

The server often listed as “iot-edge-mcp-server” (MQTT sensors, Modbus controllers, InfluxDB) has lost its original repositories: both addresses return a 404 error on 3 November 2026, and no package of that name exists on PyPI. A copy remains at lwsinclair/IoT-Edge-MCP-Server.

A community server runs with the credentials you give it. Read its code, check when it was last updated, and give it the narrowest cloud identity you can.

Safety checklist

1. Start read-only. Use the read-only setting of each server from the tables above, and widen it only after watching what the agent does.
2. Limit the cloud identity. An IAM policy or an Azure RBAC role scoped to the IoT resources the agent needs is the control that holds even if a server setting is wrong.
3. Check the authorization of remote servers. Under the MCP specification (version 2026-07-28), a protected server acts as an OAuth 2.1 resource server, must accept only tokens issued for itself (RFC 8707) and must not pass other tokens on; a token never goes in the URL query string.
4. Pin versions. Install a stated version rather than latest, as the Azure MCP Server’s npm tag shows.
5. Prefer publisher servers. Use a community server only after reading its code.

What these servers do not cover: the SIM

The servers above work on the cloud side: they see a device once it is connected, through its registry entry, its twin or shadow and its messages. The cellular line of that device is another layer: whether the SIM is active, how much data it used this month, which network it is attached to, whether it should be suspended. That layer is managed through the API of your connectivity provider.

The M2M.global MCP server is built for that layer: it lets an agent list SIMs, read their data usage, and, with a write token, suspend, reactivate or top them up, with the same permissions as the API.

Status: Coming soon (checked 26 October 2026) · Notify me when available

Device traffic can also reach your cloud without crossing the internet, through private delivery into AWS or into Azure.

How we built this guide

• Sources: publisher documentation and announcements, official GitHub repositories, PyPI and npm registries, and the GitHub API for stars and dates, all read on 3 November 2026. Each row of the CSV file gives its source address.
• Checks: each fact was matched against an excerpt of its source page, then the excerpts were checked again on the live pages the same day.
• What we looked for and did not find: an AWS server dedicated to AWS IoT Core (awslabs/mcp, AWS announcements), Event Grid MQTT tools in the Azure MCP Server, official HiveMQ and Mosquitto servers.
• These projects move fast: versions and tools change every few weeks, so we check this page every month.

Related

• MCP server for IoT SIMs
• IoT SIM API
• Deliver IoT SIM traffic privately into AWS
• Deliver IoT SIM traffic privately into Microsoft Azure