Feature
MCP servers and the Tool broker
A governed registry of Model Context Protocol tool servers, with every tool call checked at one point.
An MCP server is a registry entry for a Model Context Protocol tool server that Agents may use. It has its own Owner user, Owner group and Mode. Its secret headers are accepted on write and never shown back.
Every tool call from an Agent run passes through the Tool broker. The broker re-checks the Agent’s allow-list, validates the input, keeps headers on the server side and records an Audit event for the call. A claude-mcp Agent run takes at most 8 tool steps.
Harnesses that run outside the API call the same broker with a per-run key, and each signed request is single-use.
More features
All features →- 01
Application lifecycle
Create, configure and delete Applications with Quotas per Cluster, Namespaces, Ownership links and Extended resources.
- 02
Pipelines and Pipeline runs
Record the CI/CD definition of each Application and every execution of it, with Commit statuses beside them.
- 03
Deployment tracking
Follow each Deployment of an Application on a Cluster, with service type, DNS, Stages and Events.