For developers
Studio is a place where a team models a system. This section is for the people who connect that model to the rest of their tooling: coding agents, build machines, repositories and other systems.
You do not need any of it to model in Studio. Start with Get started if you have not used Studio yet, and see Your organization for the settings pages that several of these pages send you to.
Ways to extend Studio
Section titled “Ways to extend Studio”| You want to | Use | Who sets it up |
|---|---|---|
| Let an AI agent read and change your models | MCP | A maintainer issues the credential |
| Hand part of a model to a coding agent | Agent context | Anyone who can see the board |
| Model on a board with the coding agent you run yourself | Live modeling | Anyone with the organization’s MCP credential |
| Turn slices into code on your own machine or build server | Builders | A maintainer approves each builder |
| Keep the model next to your code | Screenplay files | Anyone who can export; a maintainer connects the repository |
| Tell another system when a board changes | Webhooks | A maintainer |
What is public and what is not
Section titled “What is public and what is not”Everything here is a surface Studio publishes on purpose: the MCP endpoint, the builder connection address, the JSON schemas and the webhook deliveries. Each one works inside one organization and only for the people or machines that organization has allowed.
Studio’s source code is not public, and nothing on these pages needs it. Where a page describes behavior, it describes what you can observe from outside.
Related
Section titled “Related”- The Screenplay language at cratis.io describes the
.playformat itself. - Glossary explains the event-modeling words these pages use.
- Build and deliver covers the same journey from the board’s side: implementation modes, progress and pull requests.