AWS IoT SiteWise
Industrial IoT asset management.
MCP server · by awslabs
About
AWS IoT SiteWise is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). The last change we recorded was on 2026-10-13. As of our marketplace pass on 2026-10-13.
What it asks for
- Runs on your machine
- Settings: 2
- Tools: 41
Tools it declares: 41. As declared on: Docker MCP Catalog.
batch_get_asset_property_aggregatesbatch_get_asset_property_valuebatch_get_asset_property_value_histconvert_multiple_timestampsconvert_unix_timestampcreate_bulk_import_schemacreate_timestamp_rangedescribe_actiondescribe_assetdescribe_asset_modeldescribe_bulk_import_jobdescribe_computation_model
Show the remaining 29
describe_computation_model_execution_summarydescribe_default_encryption_configdescribe_executiondescribe_gatewaydescribe_gateway_capability_configdescribe_logging_optionsdescribe_storage_configurationdescribe_time_seriesexecute_queryget_asset_property_aggregatesget_asset_property_valueget_asset_property_value_historyget_current_timestampget_interpl_asset_property_valuesget_metadata_transfer_jobget_sitewise_server_modelist_actionslist_asset_model_propertieslist_asset_modelslist_assetslist_associated_assetslist_bulk_import_jobslist_computation_model_data_binding_usageslist_computation_model_resolve_to_resourceslist_computation_modelslist_executionslist_gatewayslist_metadata_transfer_jobslist_time_series
What it declares, asks for and runs, in full
Only install plugins from developers you trust. We list what marketplaces publish and do not test plugins.
Works with
- Claude Code
- Codex
- Cursor
- VS Code
- Copilot CLI
A one-click link opens the client, which asks you to confirm before it adds the server.
From the marketplaces that list it and the MCP transport it declares, as each client documents them. We do not test plugins.
Connect
Commands and configs built only from what its marketplaces declare. We do not run them for you and do not test plugins.
As a local MCP server: Docker image
Built from what Docker MCP Catalog declares.
claude mcp add --transport stdio aws-iot-sitewise -- docker run -i --rm mcp/aws-iot-sitewise-mcp-server[mcp_servers.aws-iot-sitewise]
command = "docker"
args = ["run", "-i", "--rm", "mcp/aws-iot-sitewise-mcp-server"]{
"mcpServers": {
"aws-iot-sitewise": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"mcp/aws-iot-sitewise-mcp-server"
]
}
}
}docker run -i --rm mcp/aws-iot-sitewise-mcp-serverOptional settings it also lists: AWS_PROFILE, AWS_REGION.
We do not store launch arguments. If the server needs any, its own documentation names them.
Where it is published
| Marketplace | Status | Version | Figures | Verified | First seen |
|---|---|---|---|---|---|
| Docker MCP Catalog (Open on Docker Hub) | Listed | sha256:08cbb027406c | Forks (GitHub): 1 805 Pulls (Docker Hub): 12 988 Stars (Docker Hub): 0 Stars (GitHub): 9 773 |
Not marked |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
How its figures have moved
- 2026-10-1213k
- 2026-10-1313k
Each dot is a day we read a different number; flat stretches are days the number did not move. Figures of different marketplaces are never added up.
What changed
Nothing has moved on this plugin since we started watching it.
Similar plugins
Its marketplaces publish too short a description to compare this plugin with others by meaning.
Is this your plugin?
Add it to your projects and prove you maintain it with a file in its repository, a file on your domain or a DNS record. You get alerts when a marketplace lists it, drops it, changes its verified mark or what it asks for, and its remote endpoint goes on monitoring as a web service.
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.