Straight answers from what ships.
If it isn't here, ask us — we'd rather say no than oversell.
What is MakeIntelligent?
A plant stack: Console, Site Runtimes, a plant-local historian, Observe, Rules and a native MCP server. One Console per plant.
What does the MCP server actually expose?
14 tools in six toolsets — see, history, understand, monitor, act and meta: tag search and live values, history, the asset graph and impact walks, device/runtime/alarm health, and proposals.
Which AI clients work?
Any MCP client over streamable HTTP: Claude Desktop, Claude Code, Cursor, or your own agent. Console can export ready-made settings for Claude and Cursor.
Can the AI write to my PLCs?
No. The model never gets a PLC socket. Anything that would change the plant becomes a proposal a person approves in Console, and every call is audited.
Does my data leave the plant?
Not by default. History stays on the plant hub. You choose whether to use a cloud model like Claude or a plant-local OpenAI-compatible model.
Devices vs Uplinks?
Devices poll the floor on a Site Runtime. Uplinks subscribe to groups and publish outward — MQTT, Sparkplug, Kafka, Azure IoT Hub and more.
Does it run on Windows?
Yes. mii Lite is one native Windows service with a built-in Site Runtime — no Docker, WSL or VM. The same Lite package runs as a Linux service or a single k3s pod; Enterprise runs on Kubernetes.
Is it a Unified Namespace (UNS)?
mii builds the model a UNS needs: every tag sits under an ISA-95 path (Enterprise → Site → Area → WorkCenter → Equipment) and is published through MQTT uplinks to your broker. Full UNS topic trees and Sparkplug B state are on Enterprise; we show the exact topic layout in the pilot.
SSO, HA, 100+ protocols?
LDAP, HTTPS and site mTLS ship. OIDC/SAML SSO and HA are on the roadmap. We name the PLC family in the pilot contract instead of claiming 100+ drivers.
Ask your plant something real.
One line, one PLC family, live history — and an MCP URL your team can plug into Claude or Cursor.