AWS IoT SiteWise MCP Server Integration Guide
Section A: Quick Answer & Architectural Summary
The AWS IoT SiteWise Model Context Protocol (MCP) integration bridges AI coding assistants to the AWS IoT SiteWise cloud infrastructure API. It exposes 10 validated endpoint operations as callable tools for Claude Desktop, Cursor, and VS Code. Configuration is managed via hosted registry at /config/amazonaws-com-iotsitewise.json or local stdio bridge execution. Operates with zero authentication credentials out of the box. Contains 9 mutating operations (POST/PUT/DELETE); user confirmation is recommended before triggering write operations.
MCPBridge Editorial Verdict: AWS IoT SiteWise
AI coding workflows requiring programmatic access to AWS IoT SiteWise (Cloud Infrastructure) endpoints
Low (1-2 mins)
Zero Authentication Required
Automated Spec Tracking
Claude Desktop, Cursor IDE, VS Code (Cline), Zed Editor
Read & Mutating endpoints; client confirmation and least-privilege token recommended
MCPBridge rates AWS IoT SiteWise as a standardized OpenAPI-to-MCP bridge providing structured tool definitions across 10 endpoints.
Technical Overview & Protocol Integration
The AWS IoT SiteWise API, provided by Amazon Web Services, serves as the programmatic interface to the IoT SiteWise managed service, designed to ingest, model, store, and query industrial equipment data at scale. Its core capabilities revolve around defining a virtual representation of a physical industrial facility—an "asset hierarchy"—through models, assets, and properties. The API enables the creation and management of these models and assets, and critically, the ingestion of time-series data from connected industrial sensors and gateways. It provides endpoints for associating assets with projects or other assets for organizational purposes, and most importantly, for writing and retrieving time-series data. For instance, endpoints like POST /timeseries/associate and POST /properties/batch/aggregates allow for the bulk ingestion of sensor readings and the retrieval of calculated aggregates (like min, max, average), latest values, or historical data streams. Use cases span predictive maintenance, real-time monitoring of industrial operations, asset performance management, and operational analytics, allowing enterprises to transform raw IIoT data into actionable insights within the AWS Cloud ecosystem.
Exposing the AWS IoT SiteWise API via a Model Context Protocol (MCP) server delivers significant value by transforming static API documentation into an actionable, dynamic toolset for AI coding assistants. An AI agent like Claude, integrated via MCP, gains the ability to interact directly with a developer's IoT SiteWise environment. This moves beyond simple code generation to enable real-time context awareness. For example, the AI can query the actual data model of a factory floor defined in SiteWise, understand the properties of a specific compressor asset, and then generate contextually perfect code to calculate a new efficiency metric using the correct property IDs. It can automate the setup of new data ingestion pipelines by programmatically creating asset models or verifying that the necessary assets exist before writing integration code. This deep integration reduces manual lookup errors, accelerates prototyping, and allows the AI to serve as a collaborative partner that understands the live industrial data landscape the developer is working within.
Practical workflow examples demonstrate this powerful synergy. A developer could instruct an AI agent: "Query the latest temperature and pressure readings for all assets in the 'HydraulicPress' project and generate a Python script to alert if pressure exceeds 2000 PSI while temperature is above 80°C." The AI, using MCP tools, would first use the POST /projects/{projectId}/assets/associate (GET) endpoint to list relevant assets, then use POST /properties/batch/latest to fetch the current data, and finally generate precise, data-aware application code. Another dynamic task could be: "Audit the access policies attached to the 'ProductionLine' asset and update any that use overly permissive roles to the 'SiteWiseViewer' role for read-only compliance." Here, the AI could use GET /access-policies to list policies, analyze their IAM principals, and use the POST /access-policies endpoint to create new, compliant policy attachments. It could also automate bulk data backfills by writing a script that uses the POST /properties/batch/history endpoint after verifying the target assets exist.
While the API description notes "None" for authentication, it is critical to understand that all actual AWS IoT SiteWise API calls require proper AWS IAM authentication using Access Keys or temporary credentials. In a real-world MCP server implementation, securing the connection is paramount. Developers must configure the MCP server with an IAM role that adheres to the principle of least privilege. For instance, a role used by an AI assistant for read-only analysis should only have permissions like iotsitewise:GetAssetPropertyValue and iotsitewise:ListAssets, avoiding destructive permissions like iotsitewise:CreateAsset or iotsitewise:DeleteAsset. The MCP server itself must be configured to securely manage and rotate AWS credentials, and network policies should ensure the AI assistant only has access to the specific IoT SiteWise API actions and resources required for its intended tasks, preventing unauthorized data exfiltration or modification.
By translating the OpenAPI 3.0 specification for AWS IoT SiteWise into native Model Context Protocol (MCP) tool definitions, developers and AI agents gain programmatic access to endpoints over stdio or HTTP transports. Every endpoint is translated into a discrete tool payload complete with input argument validation, parameter descriptions, and return type definitions.
2. Technical Specifications Matrix
System Specifications
| API Name | AWS IoT SiteWise |
| Slug Identifier | amazonaws-com-iotsitewise |
| Category | Cloud Infrastructure |
| Auth Method | None Required |
| Endpoint Count | 10 tools mapped |
| Spec Version | OpenAPI v2019-12-02 |
| Transport Type | STDIO |
| Publisher Source | auto |
3. Multi-Client Installation Matrix
Copy and paste these pre-formatted JSON snippets into your MCP client configuration files.
Claude Desktop
Add to claude_desktop_config.json
{
"mcpServers": {
"amazonaws-com-iotsitewise": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-openapi",
"https://api.apis.guru/v2/specs/amazonaws.com/iotsitewise/2019-12-02/openapi.json"
],
"env": {
"AWS_IOT_SITEWISE_API_KEY": "your_aws_iot_sitewise_api_key"
}
}
}
}Cursor IDE
Settings → MCP Servers → Add Hosted Config
{
"mcpServers": {
"amazonaws-com-iotsitewise": {
"url": "https://mcpbridge.org/config/amazonaws-com-iotsitewise.json"
}
}
}Saves as .cursor/mcp.json in the download. Move it to your project root.
VS Code / Cline
Use with MCP extension config
{
"mcpServers": {
"amazonaws-com-iotsitewise": {
"url": "https://mcpbridge.org/config/amazonaws-com-iotsitewise.json"
}
}
}4. Security Architecture & Credentials Reference
Key parameters and credential variable mappings for AWS IoT SiteWise.
Security Considerations & Sandbox Guidance: AWS IoT SiteWise
Authorization credential isolation, least privilege boundaries, and container sandboxing options.
None Required
Read & Mutating Operations
Local MCP bridge process making outbound HTTPS requests to upstream API
Isolation & Principle of Least Privilege
Ensure outbound network access to the API endpoint is permitted. Use restricted API tokens with minimal read/write scopes.
Actionable Operational Guidelines
- Verify network firewall rules allow outbound traffic to upstream API endpoints.
- Review arguments for mutating endpoints (/assets/{assetId}/associate, /timeseries/associate/#alias&assetId&propertyId, /projects/{projectId}/assets/associate) before execution.
- Apply token rate limits and monitor usage in your provider dashboard to prevent unexpected quota consumption.
| Variable Name | Required | Example Value |
|---|---|---|
| AWS_IOT_SITEWISE_API_KEY | REQUIRED | your_aws_iot_sitewise_api_key |
5. Endpoints & Tool Schemas Matrix
Search and inspect the 10 tool signatures mapped from OpenAPI.
Executable Code Integration Examples
Call AWS IoT SiteWise endpoints via cURL, TypeScript, or Python REST SDKs.
curl -X POST "https://api.apis.guru/v2/specs/amazonaws.com/iotsitewise/2019-12-02/assets/{assetId}/associate" \
-H "Content-Type: application/json" \
# No auth requiredConcrete Real-World Use Cases for AWS IoT SiteWise
Practical multi-step agentic workflows and prompt directives demonstrating concrete developer outcomes.
Automated Contextual Workflow Integration
Practical workflow examples demonstrate this powerful synergy. A developer could instruct an AI agent: "Query the latest temperature and pressure readings for all assets in the 'HydraulicPress' project and generate a Python script to alert if pressure exceeds 2000 PSI while temperature is above 80°C." The AI, using MCP tools, would first use the POST /projects/{projectId}/assets/associate (GET) endpoint to list relevant assets, then use POST /properties/batch/latest to fetch the current data, and finally generate precise, data-aware application code. Another dynamic task could be: "Audit the access policies attached to the 'ProductionLine' asset and update any that use overly permissive roles to the 'SiteWiseViewer' role for read-only compliance." Here, the AI could use GET /access-policies to list policies, analyze their IAM principals, and use the POST /access-policies endpoint to create new, compliant policy attachments. It could also automate bulk data backfills by writing a script that uses the POST /properties/batch/history endpoint after verifying the target assets exist.
- AI assistant inspects prompt context and selects relevant tool
- Validates parameter payload against OpenAPI JSON Schema
- Executes tool call and formats structured API response
Data Inspection & Resource Querying
Query AWS IoT SiteWise resources such as "/access-policies" to retrieve contextual data directly during coding sessions.
- Agent selects /access-policies tool
- Passes search filters or resource identifiers
- Renders JSON payload in chat context for developer review
Automated Mutation & Resource Creation
Execute state changes and create records through POST operations like "/assets/{assetId}/associate" with parameter validation.
- Agent constructs validated request body matching schema
- Prompts user for execution confirmation
- Executes tool and confirms response status
Good Fit vs. Poor Fit Criteria for AWS IoT SiteWise
Architectural guidelines to determine when to adopt this integration and when to explore alternatives.
When to Choose / Good Fit
- AI coding assistants in Claude Desktop or Cursor requiring structured tool access to AWS IoT SiteWise.
- Developers who want standardized OpenAPI-to-MCP translation without building custom server code.
- Workflows that benefit from automated parameter validation against official OpenAPI 3.0 schemas.
- Teams seeking zero-maintenance hosted JSON configurations for easy distribution.
When to Avoid / Poor Fit
- Ultra-high frequency data ingestion exceeding typical LLM context windows and token rate limits.
- Unattended autonomous agent loops with write access where human approval of mutations is mandatory.
- Environments lacking outbound internet access to upstream AWS IoT SiteWise API servers.
Verification & Evidence Audit: AWS IoT SiteWise
OpenAPI 3.0 specification parsed and validated via automated build pipeline.
Independent Evidence Checks
Valid specification version 2019-12-02 with 10 endpoints indexed.
No authentication required.
JSON Schemas mapped to MCP tools/call standard format.
Automated schema validation only; live upstream API calls require developer credentials.
Project Health & Maintenance Audit: AWS IoT SiteWise
ActiveActivity & Cadence
Transparent Quality Score Breakdown
Alternatives & Comparison Table (Cloud Infrastructure)
Comparative trade-offs between AWS IoT SiteWise and similar ecosystem tools in the Cloud Infrastructure category.
| Option | Best For | Main Difference vs. AWS IoT SiteWise | Setup / Runtime | Explore |
|---|---|---|---|---|
| Access Analyzer | Developers needing Cloud Infrastructure operations with 10 tools | 10 endpoints vs 10 endpoints | auto / v2019-11-01 | View → |
| ADHybridHealthService | Developers needing Cloud Infrastructure operations with 10 tools | 10 endpoints vs 10 endpoints | auto / v2014-01-01 | View → |
| AdvisorManagementClient | Developers needing Cloud Infrastructure operations with 9 tools | 9 endpoints vs 10 endpoints | auto / v2016-07-12-preview | View → |
9. Error Resolution & Troubleshooting Guide
Contextual diagnostics for HTTP status codes and JSON-RPC tool bridge operations.
-32600 (Invalid Request)Root Cause: Malformed JSON-RPC payload sent to local MCP bridge process.
Resolution Action: Verify MCP client payload adheres to JSON-RPC 2.0 specification.
-32601 (Method Not Found)Root Cause: Requested operation does not exist in mapped AWS IoT SiteWise OpenAPI endpoint schemas.
Resolution Action: Inspect Section 5 endpoints table to confirm valid method names and paths.
-32602 (Invalid Params)Root Cause: Missing or invalid parameters for target tool operation.
Resolution Action: Check parameter data types against OpenAPI JSON Schema specification.
429 Rate Limit ExceededRoot Cause: Upstream AWS IoT SiteWise API request rate limit quota reached.
Resolution Action: Implement exponential backoff in tool execution loop or verify provider plan quotas.
OPENAPI_GATEWAY_TIMEOUTRoot Cause: Upstream AWS IoT SiteWise endpoint response latency exceeded timeout threshold.
Resolution Action: Verify network connectivity and check provider system status dashboard.
Official Verified Sources for AWS IoT SiteWise
Authoritative upstream repositories, specifications, package registries, and configuration endpoints.
Official Upstream Documentation
Official developer documentation and API reference for AWS IoT SiteWise.
https://docs.aws.amazon.com/iotsitewise/OpenAPI 3.0 Specification
Machine-readable OpenAPI schema source used for MCP tool mapping.
https://api.apis.guru/v2/specs/amazonaws.com/iotsitewise/2019-12-02/openapi.jsonHosted MCPBridge Configuration
Pre-generated Model Context Protocol JSON configuration hosted on MCPBridge.
https://mcpbridge.org/config/amazonaws-com-iotsitewise.jsonOpenAPI-to-MCP Converter Tool
Client-side browser converter to customize or filter endpoint tools.
https://mcpbridge.org/convert/Claim & Maintainer Verification
Submit a claim to verify API publisher ownership and update metadata.
https://github.com/stormlive-ai/mcp-bridge-docs/issues/new?title=Claim+Listing%3A+AWS+IoT+SiteWise+%28api%3A+amazonaws-com-iotsitewise%29&labels=claim-listing&body=%23%23+Claim+Listing+Request%0A%0AI+would+like+to+claim+this+listing%3A%0A%0A-+**Type%3A**+api%0A-+**ID%3A**+amazonaws-com-iotsitewise%0A-+**Name%3A**+AWS+IoT+SiteWise%0A%0A%23%23%23+Your+Information%0A%0A**GitHub+Handle%3A**+%3C%21--+your+GitHub+username+--%3E%0A%0A**Email%3A**+%3C%21--+optional%2C+for+verification+--%3E%0A%0A**Relationship+to+this+API%3A**%0A-+%5B+%5D+I+am+the+API+provider+%2F+maintainer%0A-+%5B+%5D+I+am+an+authorized+representative%0A-+%5B+%5D+Other%3A%0A%0A%23%23%23+Verification+Method%0A-+%5B+%5D+I+will+add+a+CNAME%2FTXT+record+to+verify+domain+ownership%0A-+%5B+%5D+I+can+confirm+from+an+email+address+at+the+provider+domain%0A-+%5B+%5D+I+maintain+the+GitHub+repository%0A%0A%23%23%23+Updates+I%27d+Like+to+Make+%28optional%29%0A%3C%21--+What+would+you+like+to+update%3F+Description%2C+links%2C+category%2C+etc.+--%3E%0A%0A---%0A*Submitted+via+MCP-Bridge+claim+form*Frequently Asked Technical Questions: AWS IoT SiteWise
Targeted developer questions regarding installation, client configuration, credentials, and error resolution.
The AWS IoT SiteWise MCP server connects AI coding assistants (Claude Desktop, Cursor, VS Code, Zed) to the AWS IoT SiteWise API using the Model Context Protocol. It converts 10 OpenAPI operations into native MCP tools callable during chat sessions.