Skip to content
Back to search

decocms

MarketplaceWorks with Claude CodeGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/decocms/studio with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/decocms/studio'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/decocms--studio/badge.svg)](/listings/decocms--studio)

HTML

<a href="/listings/decocms--studio"><img src="/api/listings/decocms--studio/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install Docker with Compose, then run from source:

git clone https://github.com/decocms/studio.git
cd studio
docker compose up --build --watch

Open [http://localhost:4000](http://localhost:4000). Compose starts PostgreSQL, NATS, object storage, migrations, and the hot-reloading API and web app. See [CONTRIBUTING.md](CONTRIBUTING.md) for contributor setup and worktrees.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 27 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "decocms",
  3. "owner": {
  4. "name": "decocms",
  5. "url": "https://github.com/decocms"
  6. },
  7. "plugins": [
  8. {
  9. "name": "decocms-ui",
  10. "source": "./packages/ui",
  11. "description": "Build UI with the decocms product design system (@decocms/ui): install, tokens, components, and conventions.",
  12. "author": {
  13. "name": "decocms"
  14. },
  15. "homepage": "https://design.decocms.com/"
  16. },
  17. {
  18. "name": "decocms-studio",
  19. "source": "./apps/api/plugin",
  20. "description": "Operate a deco Studio organization (chats, agents, tools, files) from any agent through the decocms CLI and your own login.",
  21. "author": {
  22. "name": "decocms"
  23. },
  24. "homepage": "https://decocms.com/studio"
  25. }
  26. ]
  27. }
README.md · README · 359 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <h1 align="center">deco Studio</h1>
  2. <p align="center">
  3. <em>Open-source · TypeScript-first · Deploy anywhere</em><br/><br/>
  4. <b>Open-source private AI workspace for organizations.</b>
  5. </p>
  6. <p align="center">
  7. <a href="https://docs.decocms.com/">Docs</a> ·
  8. <a href="https://decocms.com/discord">Discord</a> ·
  9. <a href="https://decocms.com/studio">decocms.com/studio</a>
  10. </p>
  11. <p align="center">
  12. <a href="https://github.com/decocms/studio/actions/workflows/test.yml"><img alt="Checks &amp; unit tests" src="https://img.shields.io/github/actions/workflow/status/decocms/studio/test.yml?branch=main&label=checks&style=flat-square"></a>
  13. <a href="https://www.npmjs.com/package/decostudio"><img alt="npm version" src="https://img.shields.io/npm/v/decostudio?style=flat-square&label=decostudio"></a>
  14. <a href="./LICENSE.md"><img alt="MIT license" src="https://img.shields.io/github/license/decocms/studio?style=flat-square"></a>
  15. <a href="https://github.com/decocms/studio/stargazers"><img alt="GitHub stars" src="https://img.shields.io/github/stars/decocms/studio?style=flat-square"></a>
  16. <a href="https://github.com/decocms/studio/graphs/contributors"><img alt="Contributors" src="https://img.shields.io/github/contributors/decocms/studio?style=flat-square"></a>
  17. <a href="https://decocms.com/discord"><img alt="Discord" src="https://img.shields.io/badge/discord-join-5865F2?style=flat-square&logo=discord&logoColor=white"></a>
  18. <br/>
  19. <img alt="Model Context Protocol" src="https://img.shields.io/badge/MCP-control%20plane-black?style=flat-square">
  20. <img alt="TypeScript" src="https://img.shields.io/badge/TypeScript-3178C6?style=flat-square&logo=typescript&logoColor=white">
  21. <img alt="Bun" src="https://img.shields.io/badge/Bun-000000?style=flat-square&logo=bun&logoColor=white">
  22. <img alt="React 19" src="https://img.shields.io/badge/React%2019-61DAFB?style=flat-square&logo=react&logoColor=black">
  23. <img alt="Hono" src="https://img.shields.io/badge/Hono-E36002?style=flat-square&logo=hono&logoColor=white">
  24. <img alt="PostgreSQL" src="https://img.shields.io/badge/PostgreSQL-4169E1?style=flat-square&logo=postgresql&logoColor=white">
  25. <img alt="OpenTelemetry" src="https://img.shields.io/badge/OpenTelemetry-425CC7?style=flat-square&logo=opentelemetry&logoColor=white">
  26. </p>
  27. > **TL;DR:** Your team needs a secure internal vibecoding platform. You just found it. Configure agents with team context. Connect private MCPs once — share capabilities, not credentials. Keep the model layer interchangeable. Roll out across the organization with SSO, RBAC, audit logs, and cost controls — all through one MCP endpoint. Local-first. Self-host or use the cloud.
  28. ---
  29. ## What is deco Studio?
  30. Studio packages the infrastructure behind an internal AI rollout: model routing, MCP authentication, agent configuration, SSO, RBAC, audit logs, and usage accounting. Your teams get chat. You keep control.
  31. Under the hood it's one control plane for your AI agents — one MCP endpoint for all your agents, tools, and models. Agents package context, tools, and policy into something you publish to the organization. Connections give them governed access to your systems — GitHub, Slack, Postgres, Sentry, anything that speaks MCP — with tokens stored in an encrypted vault. Models stay interchangeable: OpenRouter or direct providers, chosen per agent and per tool.
  32. Start with one team. Standardize approved models, tools, and context. Expand across the organization without copying secrets or rebuilding the platform. Install locally and it stays private; sync to the cloud for remote access, team roles, and shared billing.
  33. ```
  34. ┌─────────────────────────────────────────────────────────────────┐
  35. │ Clients │
  36. │ Cursor · Claude · VS Code · Custom Agents │
  37. └───────────────────────────┬─────────────────────────────────────┘
  38. │
  39. ▼
  40. ┌─────────────────────────────────────────────────────────────────┐
  41. │ DECO STUDIO │
  42. │ Agents · Connections · Models · Vault · Observability │
  43. └───────────────────────────┬─────────────────────────────────────┘
  44. │
  45. ▼
  46. ┌─────────────────────────────────────────────────────────────────┐
  47. │ Tools & MCP Servers │
  48. │ GitHub · Slack · Postgres · OpenRouter · Your APIs │
  49. └─────────────────────────────────────────────────────────────────┘
  50. ```
  51. ---
  52. ## Quick Start
  53. Install Docker with Compose, then run from source:
  54. ```bash
  55. git clone https://github.com/decocms/studio.git
  56. cd studio
  57. docker compose up --build --watch
  58. ```
  59. Open [http://localhost:4000](http://localhost:4000). Compose starts PostgreSQL,
  60. NATS, object storage, migrations, and the hot-reloading API and web app.
  61. See [CONTRIBUTING.md](CONTRIBUTING.md) for contributor setup and worktrees.
  62. ---
  63. ## What you get
  64. ### Agents
  65. Package context, tools, and policy into an agent. Define instructions, add skills and files, grant approved MCP access, choose a model policy, then publish the agent to the organization. Each agent is its own MCP endpoint — callable from Cursor, Claude Desktop, your own code, or another agent. Agents compose, and every action is tracked with cost attribution.
  66. ### Connections
  67. Connect private systems once, securely. Register MCP servers at the organization level through a web UI with one-click OAuth — no JSON configs. Tokens live in the encrypted vault, and you grant tool-level access by organization, role, or agent. Share MCP capabilities — not credentials.
  68. As tool surfaces grow, Studio exposes **Virtual MCPs** — one endpoint, different strategies for which tools to surface:
  69. - **Full-context:** expose everything (simple, deterministic, good for small toolsets)
  70. - **Smart selection:** narrow the toolset before execution
  71. - **Code execution:** load tools on demand in a sandbox
  72. ### Models
  73. Keep the AI layer interchangeable. Use OpenRouter or connect Anthropic, OpenAI, Google, or any compatible provider directly — the best model for each agent and tool, behind one router. For coding work, engineers can link their own Claude Code or Codex session and use the subscription already authenticated on their machine.
  74. ### Projects
  75. Projects bring agents and connections together around a goal. The project's UI adapts to what's inside — add a content agent and a CMS connection, the sidebar shows content management; add an analytics agent and a database, it shows dashboards and queries. The UI you see is the UI that's relevant for operating that project.
  76. ### Observability
  77. Account for every model and tool call. Trace the user, agent, model, tools, latency, errors, tokens, and cost for every thread. Break usage down by agent, connection, organization, or teammate — one dashboard.
  78. ### From your desktop to your org
  79. | | |
  80. |---|---|
  81. | **Local** | Docker Compose on your laptop, including PostgreSQL, NATS, and object storage. |
  82. | **Cloud** | Log in to studio.decocms.com. Control local projects from any browser. |
  83. | **Team** | Invite people. SSO and role-based access. Shared connections. Cost attribution. |
  84. | **Enterprise** | Self-hosted. Organization isolation, tool-scoped API keys, audit logs. Your infra, your rules. |
  85. ---
  86. ## Core Capabilities
  87. | Capability | What it does |
  88. |---|---|
  89. | **Agents** | Package context, tools, and policy into publishable agents with cost attribution |
  90. | **Connections** | Route MCP traffic through one governed endpoint with auth, proxy, and encrypted token vault |
  91. | **Models** | Interchangeable AI layer — OpenRouter or direct providers, model policy per agent |
  92. | **Projects** | Organize agents and connections around goals with an adaptive UI |
  93. | **Virtual MCPs** | Compose and expose governed toolsets as new MCP endpoints |
  94. | **Observability** | Traces, costs, errors, and latency per user, agent, and connection — one dashboard |
  95. | **Access Control** | SSO + RBAC via Better Auth — OAuth 2.1 and tool-scoped API keys per workspace/project |
  96. | **Multi-tenancy** | Organization/project isolation for config, credentials, policies, and audit logs |
  97. | **Bindings** | Capability contracts so tools target interfaces, not specific implementations |
  98. | **Store** | Discover and install agents, tools, and templates |
  99. ---
  100. ## Define Tools
  101. Type-safe, audited, observable, callable via MCP.
  102. ```ts
  103. import { z } from "zod";
  104. import { defineTool } from "~/core/define-tool";
  105. export const CONNECTION_CREATE = defineTool({
  106. name: "CONNECTION_CREATE",
  107. description: "Create a new MCP connection",
  108. inputSchema: z.object({
  109. name: z.string(),
  110. connection: z.object({
  111. type: z.enum(["HTTP", "SSE", "WebSocket"]),
  112. url: z.string().url(),
  113. token: z.string().optional(),
  114. }),
  115. }),
  116. outputSchema: z.object({
  117. id: z.string(),
  118. scope: z.enum(["workspace", "project"]),
  119. }),
  120. handler: async (input, ctx) => {
  121. await ctx.access.check();
  122. const conn = await ctx.storage.connections.create({
  123. projectId: ctx.project?.id ?? null,
  124. ...input,
  125. createdById: ctx.auth.user!.id,
  126. });
  127. return { id: conn.id, scope: conn.projectId ? "project" : "workspace" };
  128. },
  129. });
  130. ```
  131. Every tool call gets input/output validation, access control, audit logging, and OpenTelemetry traces automatically.
  132. ---
  133. ## Documentation
  134. [Studio documentation](https://docs.decocms.com/studio) lives in
  135. [docs-tanstack](https://github.com/deco-sites/docs-tanstack), alongside the
  136. Storefront documentation. Update public product guides and architecture there.
  137. Workspace READMEs and engineering plans stay here with the implementation.
  138. ## Project Structure
  139. ### Applications
  140. | Workspace | Purpose |
  141. | --- | --- |
  142. | [`apps/api`](./apps/api/README.md) | Hono API, authentication, tools, storage, migrations, and the `deco` CLI |
  143. | [`apps/web`](./apps/web/README.md) | Vite and React 19 administration interface |
  144. ### Packages
  145. | Workspace | Purpose |
  146. | --- | --- |
  147. | [`packages/bindings`](./packages/bindings/README.md) | Runtime-validated MCP capability contracts |
  148. | [`packages/create-deco`](./packages/create-deco/README.md) | `npm create deco` project scaffolding CLI |
  149. | [`packages/e2e`](./packages/e2e/README.md) | Black-box Playwright suite for Studio |
  150. | [`packages/harness-runner`](./packages/harness-runner/README.md) | In-sandbox coding-agent harness process |
  151. | [`packages/mcp-utils`](./packages/mcp-utils/README.md) | MCP proxy, gateway, aggregation, and sandbox primitives |
  152. | [`packages/runtime`](./packages/runtime/README.md) | Runtime helpers for MCP servers, OAuth, tools, and triggers |
  153. | [`packages/sandbox`](./packages/sandbox/README.md) | Agent sandbox lifecycle, daemon, dispatch, and proxy implementation |
  154. | [`packages/sandbox-controller`](./packages/sandbox-controller/README.md) | Sandbox provider bundled for a remote host such as the control plane |
  155. | [`packages/shared`](./packages/shared/README.md) | Private isomorphic contracts, SDK utilities, and async primitives |
  156. | [`packages/typegen`](./packages/typegen/README.md) | Typed client generator for Studio Virtual MCPs |
  157. | [`packages/ui`](./packages/ui/README.md) | Internal React design system |
  158. ---
  159. ## Development
  160. ```bash
  161. bun install # Install dependencies
  162. bun run dev # Docker Compose Watch: dependencies, migrations, API + web
  163. bun test # Run tests
  164. bun run check # Type check
  165. bun run lint # Lint
  166. bun run fmt # Format
  167. ```
  168. ### App-specific commands
  169. ```bash
  170. bun run --cwd=apps/web dev # Vite dev server (port 4000)
  171. bun run --cwd=apps/api dev:server # Hono server with hot reload
  172. bun run --cwd=apps/api migrate # Run database migrations
  173. ```
  174. For parallel worktrees, Compose lifecycle commands, and frontend-only work,
  175. see [CONTRIBUTING.md](CONTRIBUTING.md#getting-started).
  176. ---
  177. ## Deploy Anywhere
  178. ```bash
  179. # Docker Compose: released Studio + PostgreSQL + NATS + object storage
  180. docker compose -f selfhost/examples/docker-compose/compose.yaml up -d
  181. # Kubernetes (Helm)
  182. helm install deco-studio oci://ghcr.io/decocms/chart-deco-studio --version <version> -n deco-studio --create-namespace
  183. ```
  184. Run Studio with Docker Compose or Kubernetes on your own infrastructure.
  185. ### What you need to run it
  186. | Tier | Footprint |
  187. |---|---|
  188. | **Laptop** | Docker with Compose; the development stack includes its dependencies. |
  189. | **Docker** | Published Studio image with configured PostgreSQL, NATS, and object storage. |
  190. | **Production (Helm)** | PostgreSQL you bring, plus NATS for streaming and cross-pod coordination, ClickHouse + OTel Collector (traces and analytics), and the sandbox operator (isolated agent environments on Kubernetes). Your identity provider, your model keys, your storage. |
  191. ### Production topology
  192. ```mermaid
  193. graph TB
  194. clients["MCP clients — Cursor · Claude · VS Code · your code"]
  195. clients -->|"one MCP endpoint · SSO · RBAC · audit"| api
  196. subgraph k8s ["Kubernetes (Helm)"]
  197. api["Studio API + Admin UI"]
  198. api --> sandbox["Agent sandboxes<br/>(sandbox-operator)"]
  199. api <-->|"streams and broadcasts"| nats["NATS"]
  200. api -->|"traces · costs"| otel["OTel Collector"]
  201. nats <-->|"streams and broadcasts"| worker["Workers<br/>DBOS runs"]
  202. otel --> ch[("ClickHouse")]
  203. end
  204. pg[("PostgreSQL")]
  205. api --> pg
  206. worker <-->|"DBOS queues and journal"| pg
  207. subgraph upstream ["Models & tools"]
  208. models["Anthropic · OpenAI<br/>OpenRouter · Ollama"]
  209. mcps["GitHub · Slack · Postgres<br/>your MCP servers"]
  210. end
  211. api -->|"model routing · vaulted credentials"| upstream
  212. ```
  213. Every box is optional except Studio and PostgreSQL — start small, turn on the rest as the rollout grows.
  214. ---
  215. ## Tech Stack
  216. | Layer | Tech |
  217. |---|---|
  218. | Runtime | Bun / Node |
  219. | Language | TypeScript + Zod |
  220. | Framework | Hono (API) + Vite + React 19 |
  221. | Database | Kysely → PostgreSQL |
  222. | Auth | Better Auth (OAuth 2.1 + API keys) |
  223. | Observability | OpenTelemetry |
  224. | UI | React 19 + Tailwind v4 + shadcn |
  225. | Protocol | Model Context Protocol (MCP) |
  226. ---
  227. ## Roadmap
  228. - [ ] Agent marketplace — discover, hire, and compose agents
  229. - [ ] Declarative planning engine
  230. - [ ] Cost analytics and spend caps
  231. - [ ] Remote access from any browser
  232. - [ ] Live tracing debugger
  233. - [ ] Workflow orchestration with guardrails
  234. ---
  235. ## License
  236. **MIT** — see [LICENSE.md](./LICENSE.md).
  237. Questions? [builders@decocms.com](mailto:builders@decocms.com)
  238. ---
  239. ## Contributing
  240. ```bash
  241. bun run fmt # Format
  242. bun run lint # Lint
  243. bun test # Test
  244. ```
  245. See `AGENTS.md` for coding guidelines, [`CONTRIBUTING.md`](./CONTRIBUTING.md) for the contribution workflow, and [`TESTING.md`](./TESTING.md) for the testing rules.
  246. Good first steps: open an [issue](https://github.com/decocms/studio/issues), pick one labeled `good first issue`, or ask in [Discord](https://decocms.com/discord).
  247. ---
  248. ## Contributors
  249. Studio is built in the open. Thanks to everyone who has shipped a commit.
  250. <a href="https://github.com/decocms/studio/graphs/contributors">
  251. <img src="https://contrib.rocks/image?repo=decocms/studio" alt="Contributors to decocms/studio" />
  252. </a>
  253. Maintainers — see [`MAINTAINERS.txt`](./MAINTAINERS.txt):
  254. [@guitavano](https://github.com/guitavano) ·
  255. [@viktormarinho](https://github.com/viktormarinho) ·
  256. [@mcandeia](https://github.com/mcandeia) ·
  257. [@pedrofrxncx](https://github.com/pedrofrxncx) ·
  258. [@JonasJesus42](https://github.com/JonasJesus42) ·
  259. [@aka-sacci-ccr](https://github.com/aka-sacci-ccr) ·
  260. [@vibegui](https://github.com/vibegui) ·
  261. [@tlgimenes](https://github.com/tlgimenes) ·
  262. [@vibe-dex](https://github.com/vibe-dex) ·
  263. [@nicacioliveira](https://github.com/nicacioliveira)
  264. ---
  265. <div align="center">
  266. <sub>Made with care by the <a href="https://decocms.com">deco</a> community</sub>
  267. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.