Back to Browse
Free
Server data from the Official MCP Registry
MCP server for AWS IoT Core: device registry, shadows, jobs, rules, messaging.
About
MCP server for AWS IoT Core: device registry, shadows, jobs, rules, messaging.
Security Report
4.2
Use Caution4.2High RiskThis Eclipse Ditto MCP server implements proper authentication with environment variable credential handling and intentional permission scoping (read-only by default, explicit write/delete confirmations). The code is well-structured with good error handling. However, there are some concerns: environment variables containing sensitive credentials are read but not validated for presence before use, the devops client can be instantiated with partial/missing credentials silently, and a file truncation issue prevents full analysis of the aws-iot-core server. These are moderate quality issues rather than critical security vulnerabilities, but users should be aware of credential validation gaps. Supply chain analysis found 5 known vulnerabilities in dependencies (1 critical, 3 high severity). Package verification found 1 issue.
4 files analyzed · 13 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
AWS access key ID
Environment variable: AWS_ACCESS_KEY_ID
AWS secret access keyRequired
Environment variable: AWS_SECRET_ACCESS_KEY
AWS session token, for temporary credentialsRequired
Environment variable: AWS_SESSION_TOKEN
Named profile from ~/.aws/credentials, as an alternative to explicit keys
Environment variable: AWS_PROFILE
AWS region -- required, AWS IoT Core is regional
Environment variable: AWS_REGION
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-nagarjunr-aws-iot-core": {
"env": {
"AWS_REGION": "your-aws-region-here",
"AWS_PROFILE": "your-aws-profile-here",
"AWS_ACCESS_KEY_ID": "your-aws-access-key-id-here",
"AWS_SESSION_TOKEN": "your-aws-session-token-here",
"AWS_SECRET_ACCESS_KEY": "your-aws-secret-access-key-here"
},
"args": [
"aws-iot-core-mcp-server"
],
"command": "uvx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
IoT MCP Servers
MCP (Model Context Protocol) servers for IoT platforms — giving AI agents read access to device registries, digital twins, and telemetry.
Structure
Each server is a standalone directory under this repo — its own pyproject.toml, uv.lock, Dockerfile, and mcp.json example config. No shared library layer: every server is independently runnable and dockerizable.
<server-name>/
├── <server-name>mcpserver.py # FastMCP server (single file)
├── pyproject.toml # own dependencies
├── uv.lock
├── Dockerfile
├── mcp.json # example MCP client config
└── README.md # tools, env vars, setup for this server
Servers
| Server | Platform | Status |
|---|---|---|
eclipse-ditto | Eclipse Ditto digital twins (open source; also compatible with Bosch IoT Things and other Ditto-based deployments) | ✅ |
mqtt | MQTT 5.0 — the standard IoT pub/sub protocol (any broker: Mosquitto, EMQX, HiveMQ, AWS IoT Core, etc.) | ✅ |
More planned: Azure IoT Hub.
Running a server locally
cd <server-name>
uv sync
uv run <server-name>mcpserver.py
Using with an MCP client
Each server directory has an mcp.json with a ready-to-use client config example (Claude Desktop / VS Code / any MCP client). Copy the relevant block into your client's config, filling in the environment variables described in that server's README.
Design principles
- Read-only by default, writes explicit. Tools default to read/list operations. Any write tool is called out explicitly in that server's README. Create/replace tools default to create-only (
overwrite=False) using conditional HTTP headers rather than check-then-set, so the safe path is race-free, not just the default. Delete tools, where a server needs them, require an explicitconfirm=True— there is no bulk/cascading delete. - No vendor lock-in. Connectors target the open protocol/API (e.g. Eclipse Ditto's HTTP API), not a single vendor's proprietary extension of it, so they work against any compatible deployment.
- Tested against the real thing. Each server is verified against a real instance of the target platform (usually via Docker), not just mocks.
License
MIT — see LICENSE.
Reviews
No reviews yet
Be the first to review this server!
More Cloud & DevOps MCP Servers
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
137
Stars
558
Installs
8.0
Security
4.8
Local
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
-
Stars
87
Installs
10.0
Security
4.6
Local
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
168.6K
Stars
60
Installs
4.2
Security
5.0
Local