iTwin IoT - Claude Connector

The Bentley System iTwin IoT Claude connector is currently under review by Anthropic and will be available soon.

Overview

The Bentley iTwin IoT Claude connector gives Claude read and write access to the iTwin IoT monitoring platform: live and historical sensor data, alerts, weather context, machine learning capabilities, document references, and the asset hierarchy of any iTwins for which you have permissions. It is designed for asset operators, reliability engineers, and infrastructure asset managers who want to investigate anomalies, correlate sensor data with weather, and manage entity groups conversationally.

The connector reads only what your Bentley IMS account is already permitted to read, and writes only what you can already write — all calls are made on behalf of your authenticated identity. The connector itself has no permissions of its own.

Prerequisites

A Bentley IMS account
One or more iTwins with iTwin IoT
A Claude.ai plan that supports custom connectors (Claude Pro, Claude Team, or Claude Enterprise)

Getting started

In Claude.ai, go to Settings → Connectors and find Bentley iTwin IoT in the directory.
Click Connect. Claude will redirect you to Bentley IMS to sign in with your regular Bentley account.
Approve the itwin-platform scope when prompted.
Once authorised, the connector appears in your chat's connector list and is ready to use.

You can then ask Claude questions like the example prompts below — Claude will choose the connector when it is the right tool for the task.

Authentication

Protocol: OAuth 2.0 (OpenID Connect) against Bentley Identity Management System (IMS).
Authorization server: https://ims.bentley.com (discovered automatically by Claude via the .well-known/oauth-authorization-server endpoint).
Scope requested: itwin-platform.
Token delegation: the connector relies on standard IMS token delegation. The IMS access token issued for the connector carries your user identity (sub claim). The connector validates that token on every call and uses it to authorise the downstream iTwin IoT API request under your identity.
Transport: HTTPS only (TLS 1.2+).

What the connector can do

Capability area	Examples of what you can ask
Asset browsing	"List my iTwins", "Show the device tree for asset X."
Sensor data	"What's the latest piezometer reading on dam Y?", "Plot the temperature trend for sensor Z over the last 7 days."
Alerts	"Show me all open alerts in the last 24h for project P.", "Acknowledge alert ID 1234."
Weather	"What's the current weather at asset A's location?"
ML jobs	"What is the correlation between sensor X and sensor Y over the last 7 days?"
Entity groups	"Add device D1 to entity group `Spillway-East`."
Documents	"Get the latest inspection report for asset A."
Data export	"Export the last 30 days of sensor readings from device D as a CSV link."

A full per-tool reference, including each tool's read-only vs. destructive classification, is published alongside this page on the Bentley developer portal.

Example prompts (try these first)

"Summarise the current sensor health for my iTwin asset and call out any alerts in the last 24 hours."
"Cross-reference yesterday's high-wind weather with vibration sensor anomalies on my Yeager Airport runway slope asset."
"List devices in the entity group Spillway-East and pull the latest reading from each, then identify outliers."
"Export the last 7 days of piezometer readings from my dam asset as a CSV download link."

If you want Claude to take a destructive action — for example, deleting an ML job or acknowledging an alert — Claude will always prompt you to confirm before the call runs, because those tools are annotated as destructive in the connector.

Data handling and privacy

What we collect. When Claude calls a tool, the connector logs the authenticated user identifier (your IMS sub claim), the tool name, the duration of the call, and the outcome (success/error code). We do not log the contents of conversation messages or the raw parameter values you pass to tools. The data is kept for only 30 days and is used solely for monitoring, troubleshooting, and abuse prevention.
What we forward. Each tool call is authorised with your IMS access token. The iTwin IoT backend independently re-validates the token and enforces RBAC on every call; the connector cannot return data that your account is not entitled to.
Storage. Audit logs are stored in Bentley's Azure tenant under the same governance as iTwin IoT itself.
Third-party sharing. None beyond the iTwin IoT backend that you already use.
Retention. Audit logs follow the default Bentley operational retention for monitoring data.
Full privacy policy: see Bentley's global data privacy notice at https://www.bentley.com/legal/privacy-policy/.

Limits and quotas

To protect the iTwin IoT backend, the connector applies per-user sliding-window rate limits:

100 tool calls / 60 seconds per user (read-mostly tools).
30 tool calls / 60 seconds per user for destructive tools (delete_*, cancel_*, mutating ML-job operations).

When you hit the limit, the connector returns a structured rate_limited error and Claude will wait and retry, or surface the limit to you to decide.

Troubleshooting

Symptom	Likely cause	Fix
The connector won't connect; Claude shows a 401	IMS session expired, or sign-in cancelled	Disconnect and reconnect the connector in Claude → Settings → Connectors.
A tool returns `forbidden`	Your IMS account lacks RBAC for that iTwin or asset	Ask your iTwin admin to grant the required role.
A tool returns `not_found`	The asset/device/sensor ID does not exist or is not visible to your account	Verify the ID and your RBAC.
A tool returns `rate_limited`	Per-user quota exceeded	Wait the indicated number of seconds and retry.
A tool returns `invalid_input`	Parameters did not match the expected schema	The error message includes the failing field. Rephrase the prompt.
A tool returns `upstream_unavailable`	The iTwin IoT backend is temporarily unavailable	Try again in a few minutes; check the status page.
All tools fail repeatedly	Possible service outage	Check the status page, then contact support.