MCP & chat

Everything the console does is exposed as MCP tools. Connect your own client and drive High from your editor, an agent, or a script.

Why MCP

High has exactly two surfaces: the console and MCP. They call the same operations, so anything you can do by clicking, you can do by tool call — create projects, enroll outposts, deploy and roll back releases, read logs. The chat dock in the console is just one MCP client; yours is another.

Connect a client

Point your MCP client at your tenant's High endpoint and authenticate. The server advertises its tool set; your client discovers it automatically.

{
  "mcpServers": {
    "high": {
      "url": "https://acme.high.systems/mcp",
      "auth": "oidc"
    }
  }
}

# tools advertised by the server
create_project   deploy_release
provision_node   preview_release
component_logs   list_releases

Common tools

A deploy is one call. The engine does the rest — rendering the manifest and reconciling your outposts.

{
  "tool": "deploy_release",
  "arguments": {
    "project": "acme",
    "stage": "prod",
    "release": "r-204"
  }
}

Deploying r-204 to acme/api/prod —
the engine is rolling it out.
  api 3/3 ready · sha256:9f3c1a