IoT MCP Servers
MCP (Model Context Protocol) servers for IoT platforms — giving AI agents full read/write access to device registries, digital twins, and telemetry.
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
uvx aws-iot-core-mcp-server==0.1.0Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
AWS_ACCESS_KEY_ID=<value> AWS_SECRET_ACCESS_KEY=<secret> AWS_SESSION_TOKEN=<secret> AWS_PROFILE=<value> AWS_REGION=<value> claude mcp add io.github.nagarjunr-aws-iot-core -- uvx aws-iot-core-mcp-server==0.1.0รันในเทอร์มินัล
{ "mcpServers": { "io.github.nagarjunr-aws-iot-core": { "command": "uvx", "args": [ "aws-iot-core-mcp-server==0.1.0" ], "env": { "AWS_ACCESS_KEY_ID": "<value>", "AWS_SECRET_ACCESS_KEY": "<secret>", "AWS_SESSION_TOKEN": "<secret>", "AWS_PROFILE": "<value>", "AWS_REGION": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดEach row links to that server's README for its full tool list, required environment variables, and setup/testing notes.
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
Install straight from PyPI with uv or pipx — no clone needed:
uvx eclipse-ditto-mcp-server # or: mqtt5-mcp-server / aws-iot-core-mcp-server / azure-iot-hub-mcp-server / sparkplug-b-mcp-server
Or run from a clone of this repo:
git clone https://github.com/nagarjunr/iot-mcp-servers.git
cd iot-mcp-servers/<server-name>
uv sync
uv run <server-name>mcpserver.py
Each server reads its configuration from environment variables (connection strings, broker host, credentials, etc.) — see that server's README for the full list.
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. All servers are also listed on the official MCP registry under io.github.nagarjunr/<server-name>.
overwrite=False) — race-free via conditional headers where the target API supports them (e.g. Ditto's If-None-Match), otherwise a documented describe-then-create check. Delete tools, where a server needs them, require an explicit confirm=True — there is no bulk/cascading delete.mqtt and sparkplug-b run against a real Eclipse Mosquitto broker (sparkplug-b's tests simulate the "device" side with the same real protocol library the server uses, so both ends of the wire are genuine). aws-iot-core is tested against moto (AWS IoT Core has no free local emulator; LocalStack's IoT support requires a paid plan). azure-iot-hub is tested against respx for its REST tools; its one AMQP-only tool (send_c2d_message — Azure IoT Hub's cloud-to-device send has no REST binding) is tested against a local fake AMQP endpoint built for this repo, since no moto-equivalent exists for Azure and no free Azure IoT Hub emulator exists at all. These are genuine emulators/protocol-level fakes, not naive mocks — see each server's README for specifics and caveats.Adding a new server? Follow the structure and design principles above, add its row to the Servers table, and make sure its test suite runs against a real or faithfully-emulated instance of the target platform (document any exception, as aws-iot-core and azure-iot-hub do). Issues and PRs welcome.
MIT — see LICENSE.
MCP server for AWS IoT Core: device registry, shadows, jobs, rules, messaging.
{ "mcpServers": { "io.github.nagarjunr-aws-iot-core": { "command": "uvx", "args": [ "aws-iot-core-mcp-server==0.1.0" ], "env": { "AWS_ACCESS_KEY_ID": "<value>", "AWS_SECRET_ACCESS_KEY": "<secret>", "AWS_SESSION_TOKEN": "<secret>", "AWS_PROFILE": "<value>", "AWS_REGION": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, AWS_PROFILE, AWS_REGION
AWS IoT Core ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-10 MCP server for AWS IoT Core: device registry, shadows, jobs, rules, messaging.