Skip to content
inSCADA Docs

MCP Server

inSCADA Cloud MCP is the bridge between an AI client (Claude.ai, Claude Desktop, Claude Code) and your SCADA system. Over the Model Context Protocol it lets you read live values, follow alarms, write scripts, analyse historical data and manage animations and reports — in plain language.

The server is an address; nothing is installed on your machine:

https://mcp.inscada.online

What MCP is

Section titled “What MCP is”

The Model Context Protocol is an open protocol that lets AI clients talk to external systems in a standard way. In practice:

  • The client reaches the inSCADA API directly — there is no hand-written integration in between
  • You ask in plain language; the client calls the appropriate tools behind the scenes
  • Anything that would affect equipment asks you to confirm first

Connecting

Section titled “Connecting”

Because the server is a URL, setup is a matter of entering that address in your client’s connector settings.

In Claude.ai: Settings → Connectors → Add custom connector → paste the URL above.

Once the connector is added, the client sends you to sign in. Authorisation happens in the browser — you do not write a username and password into a configuration file.

The MCP reaches whatever spaces the account you signed in with can reach: your privileges are the ones you already have on the platform, and the MCP adds no layer of its own.

What it can do

Section titled “What it can do”

Over three hundred tools cover most of the platform: projects and spaces, connection / device / variable definitions, alarm definitions and fired alarms, trends and historical data, scripts and expressions, animations, custom HTML and menus, reports, users and roles.

Alongside those there are guide tools: before changing something in an area, the client can read that area’s rules — field names, enum values, common mistakes. This is what stops calls that fail silently because of a wrong field name.

Security

Section titled “Security”

Tools that ask for confirmation

Section titled “Tools that ask for confirmation”

Tools that affect real equipment are marked with MCP safety annotations (destructiveHint), and the client asks you to confirm before calling them:

  • inscada_set_value — writes a value to real equipment (PLC, inverter, …)
  • inscada_run_script — runs a script on the server
  • update_script — changes script code
  • inscada_api (POST / PUT / DELETE) — changes data through the general API

The session

Section titled “The session”

Authorisation is tied to the session and ends when the connection closes. Credentials are not stored on the MCP side.

Section titled “Related”