CSE ICON, Inc. sales@cse-icon.com

MCP for Geo SCADA

Ask Geo SCADA™ why, and get one answer from the live system

A read-only Model Context Protocol (MCP) server for Schneider Electric Geo SCADA, formerly ClearSCADA™. One answer from config, history, alarms, comms, and audit, instead of five screens in ViewX™.

AI assistant
Ask a question…
Send

Example conversation. Tag names and values are illustrative.

One question, one answer

The assistant does the chain of lookups an engineer would do by hand, and returns a verdict with evidence.

Why is this point stale?

Checks logging, quality, comms, sibling points, and recent changes, then tells you which one it is.

Why didn't this alarm fire?

Finds the disable, suppression, or out-of-service state that kept the alarm quiet.

Are comms to blame?

Follows a point back to its scanner and tells one broken device from one broken tag.

Is the server healthy?

Server state, redundancy role, drivers, and licence capacity in a single answer.

Whose gap is it?

Shows whether Geo SCADA held the data, so a gap downstream gets blamed on the right system.

Packaged runbooks

Ready-made prompts for failing-point triage, incident timelines, and a start-of-shift health check.

Safe on a production SCADA system

Built to read your live server without changing anything or adding load an operator would notice.

No free-form SQL

Every query is a fixed template built into the product. The assistant supplies values, never statements.

Read-only account

Connects with a Geo SCADA account that has read permission only.

Bounded queries

Every query has a row cap and a time window, so history is never scanned end to end.

Watchdog and small pool

Long-running queries are cut off, and only two connections are used because each one takes a licence slot.

Security data withheld

Credentials, access lists, and user accounts are never returned, even though the account could read them.

Gaps are reported

A failed check says "could not determine," never "nothing there," so a clean answer means clean.

Fewer tokens, lower AI cost

With skill files alone, the assistant writes queries, pulls back raw rows, and works out the answer itself. Here one tool call returns the verdict.

One call, not ten

A single diagnosis replaces the chain of lookups the assistant would otherwise run one by one.

Verdicts, not tables

Only the evidence behind the answer comes back, not every row the server looked at.

No SQL to write

Fixed queries mean the assistant never spends tokens writing, failing, and rewriting SQL.

Row caps on every query

Results are capped, so one broad question can't fill the assistant's context window.

Everything an engineer checks

The same views an engineer reaches for, available to the assistant directly.

Find any point

Search by name or class, or go straight to a point by Id or path, with exact counts.

History & coverage

Read history and check how much is actually retained before trusting an empty result.

Comms status

Sweep every channel, outstation, and scanner for active faults and silenced alarms.

Audit trail

Config changes, operator actions, and alarm history, with automated noise filtered out.

Analysis

Find gaps in a point's data, spot when a signal shifted, and compare it to its own baseline.

Knowledge base

Field notes from live systems plus the Geo SCADA help already on your machine.

Runs on the engineer's machine

A single signed executable beside your assistant. No server to expose or secure.

Ten-minute setup

Unzip the executable, create an ODBC data source, and point your assistant at it. No runtime to install.

Claude Desktop extension

Install it as a Claude Desktop extension that asks for your data source in a simple form.

Multi-system ready

Add one entry per Geo SCADA system, so points from different systems never get mixed up.

Redundancy aware

Reports which node it's connected to and whether that node is main or standby.

Offline licensing

One licence per machine, dated or perpetual, checked locally. Nothing calls home.

Signed and verifiable

The executable and its ODBC component are code-signed and timestamped by CSE ICON.

Ready to spend less time chasing stale points?

Tell us about your Geo SCADA system, and we'll set you up with a pilot.