Skip to main content

wcpd — Workstation Capability Protocol (reference server)

wcpd is the reference implementation of the Workstation Capability Protocol (WCP) — an open, vendor-neutral standard that lets an AI agent discover, understand, and operate a whole workstation under governed, audited, revocable authority.

It exposes 35 capability families / 258 operations — accessibility tree, windows, screen, files, processes, packages, services, containers, VMs, Kubernetes, git, networking, a browser (Chrome DevTools), and an RDF/PROV-O knowledge-graph view of the machine — behind least-privilege scopes, sandbox confinement, and a hash-chained tamper-evident audit log. It speaks the Model Context Protocol, so any MCP client (Claude Desktop, Claude Code, …) can use it today.

Install

pip install wcp
pip install "wcp[graph]"     # + live SPARQL (rdflib) for wcp.graph.export

Extras: graph (rdflib for live SPARQL), linux-ax (PyGObject for the Linux AT-SPI2 accessibility backend), windows-ax (comtypes for the Windows UI Automation backend).

Run

wcpd stdio     # local single-user MCP over stdio (OS session = trust boundary)
wcpd serve     # HTTP/MCP binding (workstation-addressed JWT) for networked use
wcpd doctor    # probe which capability tiers this host supports

Restricted scopes are off by default and opt-in per flag: --allow-input --allow-osa --allow-browser-eval --allow-scheduler --allow-secrets.

Security

Every operation carries exactly one scope (wcp:<family>:<class>); five restricted scopes (input:synthesize, osa:run, browser:evaluate, scheduler:control, security:secrets) are never granted by wildcard and are opt-in per flag. Filesystem-touching families are sandbox-confined; every invocation (including denials) is appended to a SHA-256 hash-chained audit log that wcp.security.audit_verify can re-check for tampering. WCP never bypasses SIP/TCC/sudo — where a capability isn't available it returns WCP_BACKEND_UNAVAILABLE rather than faking a result.

Connect to Claude Desktop

Install into a venv outside macOS TCC-protected folders, add a wcp entry to ~/Library/Application Support/Claude/claude_desktop_config.json, restart Claude Desktop, and grant Accessibility + Screen Recording. Full guide, complete capability catalog, and the normative spec: https://github.com/kchemorion/WorkstationCapabilityProtocol

License

Apache-2.0. See LICENSE.

Release files for wcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for wcp 0.1.0
File Size Uploaded
wcp-0.1.0.tar.gz 393.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for wcp 0.1.0
File Interpreter ABI Platform
wcp-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 735.7 kB

Release files / wcp-0.1.0.tar.gz

Download URL wcp-0.1.0.tar.gz
Size 393.3 kB
Tags Source
SHA-256 checksum
How to use checksums
0963e13538f91829cba5cca9366867260ca1fda8527982ad205703dc422da7c1
BLAKE2b-256 checksum
How to use checksums
e121b536d90df89523ec81a45cac4ff6d1a0274bfd7c1a261c8982621f93f159
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 3, 2026.

Transparency log

Release files / wcp-0.1.0-py3-none-any.whl

Download URL wcp-0.1.0-py3-none-any.whl
Size 342.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6822aa553f6d71dc7bf7350c3a963b4008ce2411aefbaabc8a7fa34cc9bb0638
BLAKE2b-256 checksum
How to use checksums
54f55b964a4c6e4267106c381f41c60e5b57a4cf7e44b72a83b7ef323423ccc4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 3, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page