Parked (2026-07-31). MCOS is retained as a reference LAN MCP gateway host and as the last published internal-alpha package (
vA3.12.0). It is not under active feature development and is not the orchestration path for the primary development rig.Successor for local agent orchestration: Forge-Conductor (stdio MCP tools, memory, audit, sub-agent specs) plus Grok Build on the host. Day-to-day “make software” work lives there — not in this service.
What MCOS is good for if revived: multi-machine LAN MCP fabric, Windows service packaging of a gateway host, discovery/onboarding surfaces. What it is not: an application factory or the primary agent workbench.
Artifacts to keep: GitHub pre-release vA3.12.0 (MSI + zip). Source history remains useful for installer, pool-supervision, and client-integration catalog patterns. See docs/PARKED.md.
Master Control Orchestration Server is a Windows-native LAN MCP Gateway host. It exposes one MCOS-advertised MCP endpoint for trusted-LAN clients, supervises MCP server and sub-agent worker pools, distributes onboarding profiles and CLU/Forsetti governance bundles, and provides browser plus WinUI maintainer surfaces for operations.
vA3.12.0 — Model Parity (last internal alpha pre-release; project parked)
Last package: vA3.12.0, released 2026-07-31 as a GitHub pre-release with MSI.
Previous package: vA3.11.0, released 2026-07-03. During alpha, versions used
A{alphaIteration}.{feature}.{patch}. The Windows Build, Test, and Package
workflow was the product health gate. VERSION.json remains the version authority
for the tree as frozen at park.
The product gate proved build, test, package creation, and staged bootstrapper preflight only. Without operator-authorized target-host Gate D and second-host Gate E evidence, the honest historical status at park remains alpha candidate — not deployment-certified.
Model Parity (A3.12.0) was the last released alpha milestone before park. It
adds a provider-neutral Client Integration Catalog: MCOS supports a fixed
set of external AI client and model surfaces through the governed MCP Gateway
and provider-native onboarding artifacts. The milestone is packaged as the
vA3.12.0 pre-release MSI.
The catalog registers ten canonical integrations:
claude-code— Claude Code / Desktop (Anthropic),.mcp.json.codex— Codex CLI / IDE (OpenAI),config.toml.codex-mcp-server— Codex as an external MCP server (stdio adapter).openai-responses— OpenAI Responses API remote MCP (public HTTPS).chatgpt-apps— ChatGPT Apps / Connectors (public HTTPS, OAuth 2.1).chatgpt-connector-edge— LAN-to-public connector edge bridge.xai-responses— xAI Responses / Grok API remote MCP.grok-build— Grok Build CLI / headless (xAI),.grok/config.toml.grok-build-acp— Grok Build ACP (JSON-RPC stdio adapter).generic-mcp— any MCP-compliant client.
The gateway remains the POST-only Streamable HTTP subset with no SSE; artifacts
carry only placeholder secrets. See
Client Integrations for per-provider details,
the compatibility matrix, and the /api/client-integrations routes.
Implemented in the current tree:
- Native in-process HTTP.sys MCP gateway behind
IMcpGateway. - Trusted-LAN discovery through DNS-SD/mDNS, UDP beacon,
/api/discovery, and/.well-known/mcos.json. - Per-client onboarding profiles for Claude Code, Codex, Grok, ChatGPT connector-edge, and generic MCP clients.
- CLU/Forsetti governance bundle distribution and approval workflows.
- Managed endpoint pools for MCP servers and sub-agents, with Job Object process containment, lease routing, autoscaling policy, and sticky session behavior.
- Diagnostics routes, persistent diagnostics store with JSONL fallback, browser diagnostics tab, WinUI diagnostics section, and bridge diagnostics tools.
- Optional gateway TLS through HTTP.sys certificate binding and optional admin listener TLS through SChannel.
- MSI packaging through WiX plus a zip artifact for CI/headless use.
Current limitations:
- MCOS is internal alpha software. Operator-authorized Windows host validation remains required for HTTP.sys binding, TLS binding, MSI installation, service behavior, DNS-SD visibility, and live LAN-client interoperability on each target environment before any deployment-qualified or certified working internal alpha claim.
- LAN client authentication is intentionally network-level during alpha:
auth=none, trust=lan. App-layer authentication is deferred to a later hardening track. - The native gateway implements the POST subset of MCP Streamable HTTP. Clients that require a server-initiated SSE MCP stream need a client-side bridge or a later transport expansion.
- Some validation paths depend on host toolchain availability. In particular, the WinUI Shell project requires the configured Visual Studio toolset.
- Live wiki: Master-Control-Orchestration-Server wiki
- Wiki source: docs/wiki
- Quick Start: docs/wiki/Quick-Start.md
- Configuration: docs/wiki/Configuration.md
- TLS and HTTPS: docs/wiki/TLS-and-HTTPS.md
- Gateway: docs/wiki/Gateway.md
- Worker Pools: docs/wiki/Worker-Pools.md
- API Reference: docs/wiki/API-Reference.md
- Troubleshooting: docs/wiki/Troubleshooting.md
- Versions: docs/wiki/Versions.md
- Changelog: CHANGELOG.md
- Version authority: VERSION.json
From a Windows developer shell with the repository checked out:
cmake --preset debug
cmake --build --preset debug
ctest --preset debug --output-on-failure
powershell -NoProfile -ExecutionPolicy Bypass -File scripts\check-mastercontrol-forsetti.ps1Release package flow:
cmake --preset release
cmake --build build\release --config Release
ctest --test-dir build\release -C Release --output-on-failure --timeout 300
powershell -NoProfile -ExecutionPolicy Bypass -File scripts\Package-MasterControlOrchestrationServer.ps1 -Preset release -SkipBuildThe package script reads VERSION.json. For A3.11.0, the MSI ProductVersion
mapping is 3.11.0.0 per installer/Build-Msi.ps1.
After packaging, install the MSI from the release package directory:
msiexec /i "dist\packages\release\MasterControlOrchestrationServer-vA3.11.0-win-x64\MasterControlOrchestrationServer-vA3.11.0-win-x64.msi" /l*v "$env:TEMP\mcos-install.log"Basic local checks:
& "C:\Program Files\Master Control Orchestration Server\MasterControlBootstrapper.exe" preflight --json
Invoke-RestMethod http://localhost:7300/api/health | ConvertTo-Json
Invoke-RestMethod http://localhost:7300/api/discovery | ConvertTo-Json -Depth 6
Invoke-RestMethod http://localhost:7300/api/gateway/status | ConvertTo-Json -Depth 4The current configuration file is:
%ProgramData%\MasterControlOrchestrationServer\config\master-control-orchestration-server.json
The legacy fallback name is:
%ProgramData%\MasterControlOrchestrationServer\config\master-control-program.json
See Configuration before editing the file
directly. Prefer PATCH /api/config for partial changes and reserve
POST /api/config for full-document replacement.
include/MasterControl/ Public C++ contracts, models, defaults
src/MasterControlApp/ Runtime core and gateway adapters
src/MasterControlBootstrapper/ Installer and lifecycle helper
src/MasterControlServiceHost/ Windows service and console host
src/MasterControlShell/ WinUI 3 desktop shell
src/MasterControlModules/ MCOS module registrations
resources/web/ Browser dashboard
resources/clu/ Governance profile JSON
installer/ WiX MSI source
scripts/ Existing build, package, cert, validation helpers
tests/ C++ test suite
docs/wiki/ Canonical source for the live GitHub wiki
docs/implementation/ Architecture contracts and schemas
docs/archive/ Historical evidence only
handoff/realignment/ Active realignment manifest and phase material
Forsetti-Framework-Windows-main/ Vendored Forsetti framework
Archived documents are historical evidence only. Current operator guidance lives
in docs/wiki/; current release metadata lives in VERSION.json and
CHANGELOG.md.
This project is licensed under the Apache License, Version 2.0. See LICENSE.
Outside contributions to this repository are not accepted. Pull requests and collaboration requests will not be reviewed or merged. See CONTRIBUTING.md.
Copyright (c) 2026 James Daley, Raven Forge Software
The Master Control Orchestration Server is licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.
You may use, modify, and distribute this project, including for commercial purposes. The copyright stays with James Daley, Raven Forge Software.
You must give credit to James Daley, Raven Forge Software, for the Master Control Orchestration Server. Keep that credit with every copy or product that uses this work. Keep the LICENSE and NOTICE files, keep the copyright lines in the source, and state the changes you make.