For network operators running Smallworld

A Smallworld MCP server that answers network questions under each user's own rights

A Smallworld MCP server gives Claude, ChatGPT or Copilot named tools for network assets, downstream traces and as-built changes. GE Vernova keeps the Smallworld documentation behind a login, and data access usually runs through Magik. GE Vernova ships no MCP server as of 21 September 2026, so Pexon builds one against your installation.

Why Smallworld is hard for agents

Where a Smallworld connection needs engineering, not configuration

01 · Docs

Documentation sits behind a login

GE Vernova's product documentation returns 403 without a customer login. What your installation exposes is confirmed from your documentation and your Smallworld team in the blueprint.

02 · Magik

Data access runs through Magik

Data typically comes out through Magik code inside the Smallworld image. Either your team has an existing service layer, or the read services have to be written in Magik first.

03 · Versions

The datastore is versioned

VMDS works with alternatives and checkpoints. An agent has to read the right alternative, usually the as-built one, and must never write into a design without review.

04 · Data model

Every utility customises the model

Object classes and attributes differ from one utility to the next. Tool definitions are mapped to your data model per installation, not taken from a template.

Checked 21 September 2026

Smallworld at a glance: interfaces, access and what exists for AI

	What we found
Interfaces	Smallworld Magik platform and Version Managed Datastore (VMDS) (Magik / datastore, docs behind customer or partner login): core written in Magik on the JVM, data in a versioned datastore with alternatives and checkpoints; GNM 6.0 (September 2026) adds VMDS Cloud on PostgreSQL · GridOS integration (Data Fabric, Connect, Network Update) (not published, docs not published): GNM 6.0 emphasises GridOS interoperability and data services; GE Vernova does not publish the interface specifications
Authentication	Not documented publicly. Check with GE Vernova which service layer and sign-in your Smallworld installation offers.
Vendor MCP server	No vendor server. No Smallworld or GE Vernova MCP server found; the GNM 6.0 announcement mentions AI and machine learning only as roadmap.
Vendor AI assistant	No Smallworld-specific assistant; GE Vernova's AI offerings are GridOS Visual Intelligence and industrial AI such as SmartSignal, with GridOS Data Fabric positioned as the data foundation.
Other connectors	goworld is an unofficial community Go server that exposes Smallworld data from Magik as JSON; magik-tools and an OpenAPI generator for Smallworld 5 are developer tooling, not data connectors.

GE Vernova (US). Electric, gas, water and telecom network operators that keep their as-built network model in Smallworld; GE Vernova says customers run thousands of concurrent users on a single database.

What we build

A first Smallworld tool list, written as the manifest your IT team signs

GE Vernova does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.

# smallworld-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  get_asset:           # asset ID -> attributes from the network model
    backend: confirmed in blueprint
    mode: read
  trace_downstream:    # start asset, network type -> connected downstream assets
    backend: confirmed in blueprint
    mode: read
  list_recent_changes: # area, date range -> posted as-built changes
    backend: confirmed in blueprint
    mode: read
  find_assets_in_area: # polygon or bounding box, asset class -> assets
    backend: confirmed in blueprint
    mode: read
  draft_design_note:   # asset, proposed change -> note in a design alternative for a person to review
    backend: confirmed in blueprint
    mode: propose
audit: every call logged with user, tool, arguments and the Smallworld response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

Smallworld holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.

What the connector answers, and what it will not do

Questions it answers

Which assets are connected downstream of feeder X?
Which network changes were posted to the as-built model last week in area Y?
Show the attributes and install year of cable segment Z.

What it will not do

Read more than the asking user may read in Smallworld; permissions come from Smallworld, not from the connector.
Change the as-built network: the only write tool adds a note in a design alternative for a person to review.
Replace network analysis in Smallworld: tracing and design stay in the Smallworld tools, the connector only answers questions.

When this is the wrong page

If you are moving to GNM 6.0 and GridOS, check with GE Vernova first what GridOS Data Fabric will expose, and build on that. A connector is right when Claude, ChatGPT or Copilot has to answer network questions from Smallworld today, or combine them with asset, ERP or work order data.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your Smallworld owners and checks every backend against your release and licence. Week two tests whether a person's own Smallworld permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.

What we need from you: a named Smallworld administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.

Sources: GE Vernova: Smallworld GNM · GE Vernova: GNM 6.0 (Sep 2026) · GE Vernova: geospatial technology and Smallworld · GE Vernova: GridOS Data Fabric · GitHub: goworld. Read 21 September 2026. Vendor documentation changes; verify against the current release.

Connectors for 100 source systems — the dated catalogue this page belongs to
Claude MCP server development — how we build an MCP server for any internal system

Questions Smallworld teams ask before the first tool call

Does Smallworld have its own MCP server?

Not as of 21 September 2026. We found no Smallworld or GE Vernova MCP server, and the GNM 6.0 announcement lists AI and machine learning only as roadmap. An MCP server has to be built against the service layer of your installation.

Do we need extra GE Vernova licences or access for an AI connector?

GE Vernova does not publish its interface specifications or licence terms. Check with GE Vernova which service layer and GridOS components your contract includes; the blueprint answers this before any tool is built.

Can the assistant see data a user is not allowed to see in Smallworld?

No. The connector runs each call with the asking person's own Smallworld rights and reads the as-built alternative, never a design in progress without permission. Two users asking the same question can get two different answers, and that is tested before go-live.

What does a Smallworld connector cost?

The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.

Next step

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your Smallworld administrator in the room if you like.