Components
The core MCTL platform includes the following components, each in its own repository. This page covers the core platform only, not every repository in the mctlhq organization.
mctl-api
Go REST API + MCP Server — the central control plane.
- Handles all client requests (MCP tools, REST API)
- Authenticates via MCTL sign-in (OAuth JWT)
- Submits Argo Workflows for write operations
- Tracks async operations and their status
- Exposes permission-scoped MCP tools via Streamable HTTP at
api.mctl.ai/mcp
| URL | api.mctl.ai |
| Language | Go |
| Image | ghcr.io/mctlhq/mctl-api |
| Repo | mctlhq/mctl-api |
mctl-web
Landing page and access request form — the public face of MCTL.
- Landing page at
mctl.ai - Platform MCP endpoint and OAuth are served by
mctl-apiatapi.mctl.ai/mcp - Tenant self-service creation form
- Cloudflare Worker for OAuth flows
| URL | mctl.ai |
| Language | TypeScript (Nuxt) |
| Image | ghcr.io/mctlhq/mctl-web |
| Repo | mctlhq/mctl-web |
mctl-gitops
GitOps repository — the source of declared service and platform configuration.
- ArgoCD watches this repo and syncs cluster state
- Contains Helm values, Kustomize overlays, and raw manifests
- Tenant namespaces, services, and platform config all live here
- Declared infrastructure changes are tracked in Git; workflow execution and registry state have separate stores
| URL | ops.mctl.ai (ArgoCD) |
| Repo | mctlhq/mctl-gitops |
mctl-portal
Backstage developer portal — the UI for browsing and managing services.
- Service catalog with real-time status
- Tenant and team management
- Workflow and operation history
- Custom Backstage plugins for MCTL-specific functionality
| URL | app.mctl.ai |
| Language | TypeScript (React) |
| Image | ghcr.io/mctlhq/mctl-portal |
| Repo | mctlhq/mctl-portal |
mctl-agent
Self-healing agent — automated incident response.
- Subscribes to AlertManager webhooks
- Creates tickets and stores incident state
- Analyzes alerts using Claude API plus builtin, YAML, and remote skills
- Executes skills (rollback, scale, restart, quota, probe, drift, etc.)
- Can dispatch incidents to external agents through signed webhooks
- Creates PRs to
mctl-gitopswith fixes and tracks PR metadata - Notifies operators through Telegram for updates, review, and approvals
- Full incident lifecycle: detect, analyze, propose fix, review, verify
| URL | agent.mctl.ai |
| Language | Go |
| Image | ghcr.io/mctlhq/mctl-agent |
| Repo | mctlhq/mctl-agent |
mctl-agents
Proposal agents pipeline — autonomous platform R&D and delivery loop.
- Runs service-agent cycles (researcher → analyst → spec-writer) across core repos
- Identifies documentation and implementation gaps and drafts spec proposals
- Can turn accepted proposals into pull requests through the implementer stage
- Can shepherd open PRs through review and merge
| Language | Python |
| Repo | mctlhq/mctl-agents |
mctl-docs and mctl-design
mctl-docs publishes the VitePress documentation at docs.mctl.ai. mctl-design owns shared colors, typography, site layout tokens and versioned CSS at ui.mctl.ai. The Nuxt landing and VitePress docs consume the same pinned design release.