Status: Accepted · Date: 2026-07-02
ADR-0002 established an MCP-first control plane for the CloudSpatial platform. The owner has since narrowed and elevated the goal: the workstation server's contract should itself be the product — a vendor-neutral standard that third-party applications, AI agents, and operating systems can adopt independently. The wider platform (AI desktop agent, gateway, streaming, billing) is deferred.
- The standard is named the Workstation Capability Protocol (WCP).
Operation namespace
wcp.*, scope namespacewcp:*, vendor extensions underx-<vendor>.*. This repository is dedicated to WCP. - WCP is layered as a wire-neutral core capability model (families,
versioned operations with JSON Schemas, self-describing manifest via
wcp.system.describe, scope + audit requirements) plus bindings; MCP is the first normative binding. Future REST/gRPC/OS-native bindings do not reopen the core. - The deliverable is a full standards package: prose spec,
machine-readable schemas, a standalone conformance suite, and a
reference implementation (
wcpd) with real adapters for Linux, macOS, Windows, and a container profile. - Security invariant carried into the spec: scopes marked restricted
(v0.1:
wcp:input:synthesize) are never matched by wildcards, including*— they must be granted verbatim.
- Repo layout puts the standard at the root (
spec/,schemas/,conformance/), with the server relocated toreference/wcpd/and its package renamed fromcloudspatial_mcptowcpd. - ADRs 0001 (remote display) and 0002 remain as historical origin; 0001 concerns a future consumer platform and is not binding on this repo.
- Conformance, not implementation, defines the standard: any server that passes the suite is WCP-conforming regardless of language or vendor.