AWS IoT SiteWise MCP Server
AWS Labs MCP server for SiteWise asset models, time series, and related industrial data in an AWS account.
Who it's for
An engineer attaching an MCP client to no field protocol. Treat the write policy as the safety boundary: a gated write is still a write once you arm it.
Caveat / limitations
Open-source server in awslabs/mcp. It calls SiteWise APIs in your account, so IAM is the real permission boundary and SiteWise itself is a paid AWS service. It does not speak Modbus or OPC UA; something else has to land data in SiteWise first. Asset writes and ingestion tools are part of the surface. Keep the IAM policy narrower than the demo.
Protocols
No field protocol or IEC language is claimed. If this tool reaches a PLC, it does so through something else already named in the notes.
Sources
- Docshttps://awslabs.github.io/mcp/servers/aws-iot-sitewise-mcp-server
- Sourcehttps://github.com/awslabs/mcp/tree/main/src/aws-iot-sitewise-mcp-server
This page: https://otaihub.com/tools/aws-iot-sitewise-mcp
Same category
- CODESYS Development System MCP ServerOfficial CODESYS add-on that lets an MCP client read and write the open project, compile, and fix Structured Text.
- IndustriConnect Modbus MCPOpen-source Modbus TCP, UDP, and RTU client for MCP hosts, with a mock device and writes off by default.
- IndustriConnect OPC UA MCPPython and Node OPC UA MCP servers with the same tools: browse, read, history, alarms, and gated writes.
- IndustriConnect MQTT / Sparkplug MCPMQTT client that publishes, subscribes, and decodes Sparkplug B instead of handing the model raw bytes.