
AWS IoT Core
io.github.nagarjunrPublished by GitHub account nagarjunrv0.1.0Updated Oct 24, 2026
MCP server for AWS IoT Core: device registry, shadows, jobs, rules, messaging.
The publisher's own server: core.blue
Overview
Local MCP server for AWS IoT Core that lets an assistant manage devices, shadows, jobs, certificates, policies and rules in an AWS account.
- What you can do
- List, search, create, update and delete things, thing types and thing groups, including group membership and fleet-index queries (search needs indexing enabled). Read, update and delete classic or named device shadows, and list named shadows per thing. Publish MQTT messages to the device fleet through the IoT Data Plane. Create, list, cancel and delete fleet jobs and track per-device job executions. Manage device auth: generate key pairs and certificates, set certificate status, and create, attach and delete IoT policies. List, create, enable, disable and delete SQL-based topic rules, and look up the account's IoT data endpoint.
- When to use it
- Useful when an assistant should inspect or operate an AWS IoT Core fleet from a local session: auditing registered devices, reading or updating shadow state, pushing OTA or remote-command jobs, or reviewing message routing rules. It is scoped to IoT Core only, not Greengrass, SiteWise, Device Defender or TwinMaker.
- Requirements
- Runs locally as a Python package via uvx (stdio). Needs AWS credentials through the standard SDK chain: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and optionally AWS_SESSION_TOKEN, or AWS_PROFILE, or an attached IAM role. AWS_REGION is required because IoT Core is regional; AWS_ENDPOINT_URL can override the endpoint. Network access to AWS is needed.
Installation
In SourceWeft
- Open AWS IoT Core in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AWS IoT Core MCP Server
A Model Context Protocol (MCP) server for AWS IoT Core — device registry, device shadows, jobs (fleet management), the rules engine, and messaging.
Scoped deliberately to IoT Core itself: no Greengrass (separate edge-deployment API), no IoT SiteWise (already has an official awslabs MCP server), no Device Defender/Events/TwinMaker — each of those is its own AWS service with its own API and would be its own connector.
Tools
Things (device registry)
Thing Types & Thing Groups
Device Shadows (data plane)
Messaging
Jobs (fleet management)
Certificates & Policies (device auth)
Rules Engine
Misc
Safety conventions
Same as the rest of this repo: create_*/put_* default to overwrite=False (best-effort — the AWS IoT API itself has no conditional-write header for most of these operations, so this is a describe-then-create check, not fully race-free like Ditto's If-None-Match). Every delete_*/cancel_* requires confirm=True.
Configuration
Standard AWS SDK credential resolution — no custom env vars for auth. Set whichever of these your setup uses:
Or an IAM role, if running somewhere with one attached (EC2/ECS/Lambda). See boto3's credential docs.
Running locally
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. AWS IoT Core has no official local emulator, and LocalStack's IoT support requires a paid plan (no free tier) — so this server is the one exception in this repo: tests run against moto, a mature, free, open-source AWS API emulator (not hand-rolled mocks — it implements real request/response behavior for the actual boto3 calls this server makes).
License notes
No bundled deployment artifacts here (unlike the other servers) since there's no local broker/service to run — AWS IoT Core only exists as an AWS-hosted service.
Source: aws-iot-core/README.md at commit 5a985b6
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Core integrations
core.blue
blue.coreOfficial publisher
Remote MCP endpoint for core.blue's private per-customer agent memory "houses": read its manual, try a sandbox, get pricing and recommendations, and request a…

Entity Bind - Core
Published by GitHub account Tenhaw
Company resolution and enrichment with decision receipts, as a remote MCP server.

Multiplatform core design — Atom
org.aimlds
Multiplatform core design — Atom's hosted MCP server, published by aimlds.org; credential required; Streamable HTTP.
Senrelay (ContextCore)
Published by GitHub account qingsongcui
Local macOS multi-agent session relay (/contextcore), source-linked memory, and 15-host MCP sync.
CoreScout
com.tensorust
Local-first memory for your machine: it observes commands, failures and verified fixes, and lets an AI ask what has gone wrong here before acting.