Skip to content

AI²
Version 2.0.0 (tag v2.0.0-release, 2026-10-23)
Helm subchart ai2 of oop-platform-chart (MCP server, AI agent and Redis)
Artefacts labs.etsi.org:5050/oop/code/ai2/mcp_module:2.0.0, labs.etsi.org:5050/oop/code/ai2/ai_agent:2.0.0
Specs ai2/
Changes v1.0.0-release...v2.0.0-release

AI² ("AI squared") is the natural-language agent of OpenOP. In this release it works on the OEG 2.0 APIs: it manages edge applications, QoD sessions and Traffic Influence, and retrieves device location. Every call it makes to OEG carries the user's own token, so the user's roles decide what AI² may do.

New in this release

AI² has two modules:

  • MCP server (mcp_module): exposes OEG's CAMARA APIs as MCP tools.
  • AI agent (ai_agent): a FastAPI backend that runs a Groq-hosted model over those tools, with a short per-session memory in Redis.
API Tools
Edge Application Management Register, list, read and delete applications; instantiate, list and delete instances; create, list and delete deployments; list zones
Quality on Demand Create, read and delete a session
Traffic Influence Create, list, read and delete; create for a single device
Location Retrieval Retrieve a device's location

OEG's error messages reach the user, and the agent can chain several tools in one request.

Breaking changes

  • The AI agent moves from Quart to FastAPI.
  • Tools target OEG 2.0. The 1.x tools are removed.
  • Every request needs a Keycloak token. Set AUTH_ENABLED=false only on platforms deployed without login.
  • Redis holds the agent's memory. The chart deploys it; memory is used only when REDIS_URL is set.
  • Helm chart 2.0.0. On Kubernetes, AI² is deployed by the ai2 subchart of oop-platform.

Upgrade notes

Give the Groq API key in ai2.secrets.groqApiKey. Without it the agent deploys, but chats fail. The oop-platform chart points the MCP server at OEG.

Known limitations

The full list is in the spec's Implementation & Delivery › Known Gaps. The main ones:

  • The agent does not validate tokens; it only forwards them to OEG. Do not expose the agent or the MCP server outside the cluster. The kind environment publishes both on NodePorts for local development only.
  • User prompts and tool results are sent to Groq.
  • Memory is not tied to the caller. Set redis.enabled: false to turn it off.
  • No confirmation before writes, and no time budget. A retry can repeat a create.
  • No federation tools. Use the Portal's Federation page.
  • Some OEG operations have no tool.
  • Health checks do not cover Groq, Redis or OEG, and /debug/objgraph needs no token.
  • Containers run as root, with no resource requests or limits.
  • The repository READMEs are partly out of date; the spec is the reference.