Protocol specification
Deploy Context
Protocol (DCP)
An open publishing interface for people and AI agents. Specification coming soon.
An open publishing interface
The Deploy Context Protocol (DCP) defines a common interface for publishing and managing projects. The specification is coming soon; the interface below is a proposal, not a callable API.
The intended transports are remote MCP and HTTPS/JSON. Unclaimed deployment is designed to work without signup, followed by a private claim link that gives the person ownership. Claimed projects would use bearer-token authentication.
Planned DCP tools
| Tool | Purpose |
|---|---|
deploy | Publish a creation and return its URL, app ID, claim link, and expiry information. |
status | Read project state, version, resources, and last request. |
logs | Understand how the published project is behaving. |
exec | Run a bounded command within a project. |
env.set / env.list | Manage configuration; secret values remain write-only. |
rollback | Return to a previous version. |
delete | Remove a project through an explicit, authorized action. |
Static publishing, status, logs, deletion, and the claim flow form the first planned release. Execution, environment settings, and rollback belong to the application-runtime stage.
Clear results and room to continue
The proposed deploy result includes url, app_id, claim_url, and expires_at. Capacity responses should include a retry time; archived projects should provide a clear route to restoration where available.
Full export, stable URLs, and understandable retention rules are design goals. The released specification will define the exact schemas and behaviour.
Developing the standard in the open
We plan to publish the specification under CC BY 4.0 and reference code under Apache 2.0, with public proposals, review, and versioned releases.