by decocms
Open-source control plane for your AI agents. Connect tools, hire agents, track every token and dollar
# Add to your Claude Code skills
git clone https://github.com/decocms/studioTL;DR: Hire agents. Connect tools. Organize them into projects with a UI that fits the job. Track every token and dollar. Self-host or use the cloud.
Studio is where you hire agents, connect tools, and organize them into projects that actually do things.
Agents come with real skills and battle-tested prompts. Connections give them access to your tools — GitHub, Slack, Postgres, OpenRouter, anything that speaks MCP — set up through a web UI with one-click OAuth. Projects bring agents and connections together around a goal: each project gets its own sidebar and UI, shaped by what's inside it.
Everything is tracked — tokens, costs, errors, latency — per connection, per agent. Install locally and it stays private. Sync to the cloud for remote access, team roles, and shared billing.
┌─────────────────────────────────────────────────────────────────┐
│ Clients │
│ Cursor · Claude · VS Code · Custom Agents │
└───────────────────────────┬─────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ DECO CMS │
│ Agents · Connections · Projects · Observability · Token Vault │
└───────────────────────────┬─────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ Tools & MCP Servers │
│ GitHub · Slack · Postgres · OpenRouter · Your APIs │
└─────────────────────────────────────────────────────────────────┘
bunx decocms
Or clone and run from source:
No comments yet. Be the first to share your thoughts!
git clone https://github.com/decocms/studio.git
bun install
bun run dev
runs at http://localhost:3000 (client) + API server
Browse and hire specialized AI agents from the built-in store. Each agent knows how to use specific tools and comes with battle-tested prompts. Agents compose — they can call each other — and every action is tracked with cost attribution.
Set up MCP connections through a web UI with one-click OAuth. No JSON configs. Monitor latency, errors, and costs per connection. Share tools across your team without sharing credentials.
As tool surfaces grow, Studio exposes Virtual MCPs — one endpoint, different strategies for which tools to surface:
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.
You can also define outcomes declaratively and let Studio work backward to derive milestones, assign agents, and verify results.
Token spend per connection — OpenRouter, Perplexity, Firecrawl, all of it. Latency, errors, bottlenecks. One dashboard.
| | |
|---|---|
| Local | bunx decocms on your laptop. Embedded PostgreSQL. Private. |
| Cloud | Log in to studio.decocms.com. Control local projects from any browser. |
| Team | Invite people. Roles. Shared connections. Cost attribution. |
| Enterprise | Self-hosted. Your infra. Your rules. |
| Capability | What it does | |---|---| | Agents | Browse, hire, and compose AI agents with tracked skills and cost attribution | | Connections | Route MCP traffic through one governed endpoint with auth, proxy, and token vault | | Projects | Organize agents and connections around goals with an adaptive UI | | Virtual MCPs | Compose and expose governed toolsets as new MCP endpoints | | Observability | Traces, costs, errors, and latency per connection — one dashboard | | Access Control | RBAC via Better Auth — OAuth 2.1 + API keys per workspace/project | | Multi-tenancy | Workspace/project isolation for config, credentials, policies, and audit logs | | Event Bus | Pub/sub between connections with scheduled/cron delivery and at-least-once guarantees | | Bindings | Capability contracts so tools target interfaces, not specific implementations | | Store | Discover and install agents, tools, and templates |
Type-safe, audited, observable, callable via MCP.
import { z } from "zod";
import { defineTool } from "~/core/define-tool";
export const CONNECTION_CREATE = defineTool({
name: "CONNECTION_CREATE",
description: "Create a new MCP connection",
inputSchema: z.object({
name: z.string(),
connection: z.object({
type: z.enum(["HTTP", "SSE", "WebSocket"]),
url: z.string().url(),
token: z.string().optional(),
}),
}),
outputSchema: z.object({
id: z.string(),
scope: z.enum(["workspace", "project"]),
}),
handler: async (input, ctx) => {
await ctx.access.check();
const conn = await ctx.storage.connections.create({
projectId: ctx.project?.id ?? null,
...input,
createdById: ctx.auth.user!.id,
});
return { id: conn.id, scope: conn.projectId ? "project" : "workspace" };
},
});
Every tool call gets input/output validation, access control, audit logging, and OpenTelemetry traces automatically.
├── apps/
│ ├── mesh/ # Full-stack Deco CMS (Hono API + Vite/React)
│ │ ├── src/
│ │ │ ├── api/ # Hono HTTP + MCP proxy routes
│ │ │ ├── auth/ # Better Auth (OAuth + API keys)
│ │ │ ├── core/ # MeshContext, AccessControl, defineTool
│ │ │ ├── tools/ # Built-in MCP management tools
│ │ │ ├── storage/ # Kysely DB adapters
│ │ │ ├── event-bus/ # Pub/sub event delivery system
│ │ │ ├── encryption/ # Token vault & credential management
│ │ │ ├── observability/ # OpenTelemetry tracing & metrics
│ │ │ └── web/ # React 19 admin UI
│ │ └── migrations/ # Kysely database migrations
│ └── docs/ # Astro documentation site
│
└── packages/
├── bindings/ # Core MCP bindings and connection abstractions
├── runtime/ # MCP proxy, OAuth, and runtime utilities
├── ui/ # Shared React components (shadcn-based)
├── cli/ # CLI tooling (deco commands)
├── create-deco/ # Project scaffolding (npm create deco)
└── vite-plugin-deco/ # Vite plugin for Deco projects
bun install # Install dependencies
bun run dev # Run dev server (client + API)
bun test # Run tests
bun run check # Type check
bun run lint # Lint
bun run fmt # Format
apps/mesh/)bun run dev:client # Vite dev server (port 4000)
bun run dev:server # Hono server with hot reload
bun run migrate # Run database migrations
dev:worktree routes http://<WORKTREE_SLUG>.localhost via Caddy — useful for running multiple workspaces without port conflicts.
# One-time setup
brew install caddy && caddy start
# Start
WORKTREE_SLUG=my-feature bun run dev:worktree
# Conductor adapter (sets WORKTREE_SLUG from CONDUCTOR_WORKSPACE_NAME)
bun run dev:conductor
# Docker (embedded PostgreSQL)
docker compose -f deploy/docker-compose.yml up
# Docker (PostgreSQL)
docker compose -f deploy/docker-compose.postgres.yml up
# Bun
bun run build:client && bun run build:server && bun run start
# Kubernetes (Helm)
helm install deco-studio oci://ghcr.io/decocms/chart-deco-studio --version <version> -n deco-studio --create-namespace
No vendor lock-in. Runs on Docker, Kubernetes, AWS, GCP, or local runtimes.
| Layer | Tech | |---|---| | Runtime | Bun / Node | | Language | TypeScript + Zod | | Framework | Hono (API) + Vite + React 19 | | Database | Kysely → embedded PostgreSQL / PostgreSQL | | Auth | Better Auth (OAuth 2.1 + API keys) | | Observability | OpenTelemetry | | UI | React 19 + Tailwind v4 + shadcn | | Protocol | Model Context Protocol (MCP) |
Sustainable Use License (SUL) — see LICENSE.md.
Questions? builders@decocms.com
bun run fmt # Format
bun run lint # Lint
bun test # Test
See AGENTS.md for coding guidelines.