AWS IoT Core logo

AWS IoT Core

Connects AI agents to AWS IoT Core for registry, shadow, job, rule, and messaging operations.

Install AWS IoT Core

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aws-iot-core": {
      "command": "uvx",
      "args": [
        "eclipse-ditto-mcp-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx eclipse-ditto-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 5d ago.

Overview

The AWS IoT Core MCP server exposes AWS IoT Core capabilities to AI agents through 48 MCP tools. It covers device registry, shadows, jobs, rules, and messaging, with read and write access described for the IoT server family. Install it as a standalone Python package with uvx, or run it from a cloned repository. Reach for it when an MCP client needs to inspect or manage AWS IoT Core resources.

Use cases

  • Inspect AWS IoT Core device registry resources
  • Manage device shadows through an MCP client
  • Work with IoT jobs and rules
  • Send or handle IoT messaging operations

Key features

  • 48 MCP tools
  • Device registry access
  • Device shadow support
  • IoT jobs and rules
  • IoT messaging
  • Standalone Python package

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · eclipse-ditto-mcp-server (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit12d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How AWS IoT Core works

What AWS IoT Core MCP server does

The AWS IoT Core MCP server connects an MCP-compatible AI client with AWS IoT Core. Its 48 tools cover the platform areas listed by the project: device registry, shadows, jobs, rules, and messaging. This gives an agent a structured way to work with AWS IoT Core instead of relying only on free-form instructions or external scripts.

The repository describes its IoT servers as providing read and write access to device registries, digital twins, and telemetry. For AWS IoT Core specifically, the supported resource areas are the registry, shadows, jobs, rules, and messaging.

How it works

Each connector in the repository is an independent Python server. The AWS implementation has its own project configuration, lockfile, Dockerfile, MCP client configuration example, and server entry point rather than depending on a shared library layer.

The server communicates with AWS IoT Core through the platform-specific connector. It is not presented as a cross-vendor abstraction: the repository explicitly treats AWS IoT Core as a vendor-specific service. The project tests this connector against moto because AWS IoT Core does not have a free local emulator. That testing choice is useful context when evaluating behavior that depends on the complete AWS service rather than the emulator.

Setup and configuration

The project requires Python 3.12 or newer and uses uv for dependency management and execution. The published package can be launched without cloning the repository:

bash
uvx aws-iot-core-mcp-server

From a checkout, enter the aws-iot-core directory, install dependencies with uv sync, and start the server with the directory's Python entry point. The server reads its connection details and credentials from environment variables.

An mcp.json example is included in the server directory. Copy its relevant configuration into an MCP client's settings and fill in the required environment variables. The repository specifically identifies Claude Desktop and VS Code as supported configuration targets, while also describing the setup as usable with any MCP client.

Tools and capabilities

The documented capability groups are:

  • Device registry access
  • Device shadow operations
  • IoT jobs
  • IoT rules
  • IoT messaging

The server advertises 48 tools across these areas. The material does not specify which tools are read-only, which mutate resources, or whether individual operations require confirmation. Review the AWS IoT Core server README for those distinctions before granting it production credentials.

Limitations and notes

AWS IoT Core is inherently tied to AWS, so this connector does not provide the repository's broader cross-vendor abstraction described for open protocols. Local testing uses moto rather than a free, complete AWS IoT Core instance; the repository notes that LocalStack IoT support requires a paid plan.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about AWS IoT Core

AWS IoT Core is an MCP server that connects AI agents to AWS IoT Core and exposes 48 tools for device registry, shadows, jobs, rules, and messaging. It runs as a standalone Python 3.12+ package and uses configuration supplied through environment variables.

Install it with `uvx aws-iot-core-mcp-server`. You can also clone the repository, enter the `aws-iot-core` directory, run `uv sync`, and start the server from its Python entry point.

It supports device registry, shadows, jobs, rules, and messaging through 48 MCP tools.

Yes. The repository includes an `mcp.json` example for Claude Desktop and VS Code, and states that the servers can be configured with any MCP client. Required environment variables must be filled in from the server README.

Testing uses moto because AWS IoT Core has no free local emulator. The repository notes that LocalStack IoT support requires a paid plan, so local emulator coverage may not match the complete AWS service.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAWS IoT Core AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aws-iot-core?style=directory)](https://allmcps.com/mcp/aws-iot-core)
HTML Embed
<a href="https://allmcps.com/mcp/aws-iot-core"><img src="https://allmcps.com/api/badge/aws-iot-core?style=directory" alt="AWS IoT Core on AllMCPs" /></a>