Agent MCP
HEAT can expose its knowledge base and, when you allow it, live platform data to AI agents over the Model Context Protocol (MCP), a standard interface that agent clients use to call tools. The Agent MCP page controls exactly what those agents can see and do. Open Developer Tools, then Agent MCP (/admin/developer-tools/agent-mcp).
Changes take effect on the next request, with no service restart. The page confirms with a message that the change is live.
Turning it on
A master Enable agent access switch turns the MCP endpoint on. While it is off, agent clients cannot connect at all. With it on and every scope below off, agents can still read HEAT’s documentation, platform status and release information, but no project or session data.
Presets and scopes
Quick presets set a whole posture at once: Documentation only, Read-only integration, Full inspection and Automation. You can then adjust each scope by hand. Every scope defaults to off.
| Scope | Read allows | Write allows |
|---|---|---|
| Projects | List and inspect projects | Create and update projects |
| Sessions | List, search and inspect sessions, their nodes and timeline | Create sessions |
| Templates | List and inspect session and node templates | Create session templates |
| Runners | List runner types and tasks | Nothing further today |
Output data is gated separately. Session outputs takes Off, Metadata or Data. Metadata exposes output records, storage paths and configuration with no access to the stored bytes. Data adds the stored bytes, subject to a size cap.
Choosing a posture
Sessions set to Read together with outputs set to Data exposes training data bytes to any agent holding a valid token. In production, prefer Metadata or Off. Any Write scope lets an agent change platform state, so audit who holds tokens.
Agents authenticate with the same tokens as other integrations, including offline tokens. The Client setup tab gives connection snippets for common agent clients and a connectivity check. The page also lists what stays available to agents regardless of the scopes, and what remains visible only inside the Control Centre.