decocms-studio plugin
An agent plugin that operates a deco Studio organization from the terminal under your own sign-in, through the decocms CLI
- 414 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent acts in Studio in your name: it reads the organization's chats and files and calls tools that can delete and overwrite data
- Sharing a file by link opens it to anyone with the link, and when the CLI is not on PATH the latest package version runs through bunx
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/decocms-studioDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent acts in Studio in your name: it reads the organization's chats and files and calls tools that can delete and overwrite data
- Sharing a file by link opens it to anyone with the link, and when the CLI is not on PATH the latest package version runs through bunx
This is third-party code. Review the repository files before installing.
What it does
deco Studio is an open control plane for AI agents in organizations: MCP connections, agents, chats, usage accounting, SSO and access rights. The repository holds the platform itself, and for agents it carries the decocms-studio plugin with a skill of the same name. The skill teaches the agent to work with Studio through the decocms CLI. First the agent checks the session with `decocms auth whoami`, then learns the organization slug through `decocms orgs`. After that the main route is built-in tools: `decocms tools list` finds them, `decocms tools describe` shows the schema and `decocms tools call` invokes them. Features without tools, such as the organization's file system (the Library), sending a message to an agent and streaming its reply, are reached through `decocms api` in the manner of `gh api`. The skill distinguishes a chat from a thread, an agent from a virtual MCP, a connection from an organization's MCP server and a file system volume. Operations flagged destructiveHint need the user's explicit go-ahead for that specific call, and the agent shares a file only when you ask.
Who it is for. For teams that already run deco Studio and want to read chats, manage agents and organization files from Claude Code or another agent.
Good fit when
- You want to read the organization's latest chats in Studio and summarise what the agents have been doing
- You want to send a message to a Studio agent from the terminal and get a streamed reply
- You want to put a file into the organization's Library or check that it is there and get a link
- You want to review MCP connections and monitoring of the organization without opening the web interface
- Studio runs locally or on your own server: the address is set with the `--target` flag
Not a fit when
- You have no organization in deco Studio: the plugin works only with that platform
- You need sign-in with an API key, an MCP token or a presigned URL: the skill explicitly forbids working around the session this way
- The agent must not change organization data: deletion, overwriting and file sharing are available through tools and routes
- You need a native MCP server with no CLI: this plugin works through the decocms command
Example request
Show which chats took place in our Studio organization over the last day and send me the link to the longest one.Limitations
The plugin needs the decocms CLI and an active session: sign-in runs through `decocms auth login`, which opens a browser, and the agent does not run it itself. The CLI runs on Bun, also when started through npx. If Bun is missing, the agent should ask you before installing it with a script.
When the command is not on PATH, the skill runs `bunx decocms@latest`, which executes the latest published package version. The message `Unknown command: tools` means a stale cache, and then you run `bunx decocms@latest`.
A second plugin sits next to it in the repository, decocms-ui with design system rules, and it is described separately. Whether deco Studio is reachable from Russia was not checked for this card. The plugin's install commands are derived from the marketplace.json file at the repository root.
How to disable. Remove the plugin with `/plugin uninstall decocms-studio@decocms`.
FAQ
How do I install the decocms-studio plugin in Claude Code?
Run `/plugin marketplace add decocms/studio`, then `/plugin install decocms-studio@decocms`. The marketplace.json file describes the plugin as a way to operate a Studio organization from any agent through the decocms CLI.
How do I sign in to Studio from the plugin?
`decocms auth whoami` shows the target and the user. If there is no session, the agent hands you `decocms auth login`: you run it in your own terminal and approve the sign-in in a browser. The session refreshes itself, so sign-in is normally needed once per machine.
How do I work with my own Studio server?
Add the `--target <address>` flag to every command, for example `--target http://localhost:3000`. A local or self-hosted Studio uses the same CLI.
How does the agent find the right organization?
`decocms orgs` prints the slug and name of each organization. If you named a project, the search goes through `decocms api` on the projects route, and with several matches the agent asks you.
Can the agent delete data in Studio?
Technically tools flagged destructiveHint allow it, but the skill requires the user's explicit go-ahead for each such call. The agent turns on file sharing by link or password only on request and after confirming the mode.
Discussion
No questions or reviews yet.
Related
PluginsA terminal session manager for Claude Code, Codex, Gemini CLI, OpenCode and other agents: one list with statuses, git worktrees and control from a phone
Director bundles MCP servers, prompts and settings into playbooks and serves them to an agent through one endpoint, with central OAuth and tool filtering
Multi-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents
A skill with 25 commands to audit and improve the prompts, tools and agent designs of a project in Cursor, Claude Code and Codex
A CLI to run several coding agents: one config, a session console, local memory and a set of engineering skills
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| decocms-studio (this entry) | yes | 414 | ||
| Mission Control | yes | API key | 6,410 | a self-hosted panel for running several agents, while this plugin operates an existing deco Studio from the terminal |
| MCP Gateway Registry | no | OAuth | 1,022 | a registry and gateway for MCP servers with a shared login, while the plugin works through the CLI of one platform, deco Studio |
README in short
The page presents deco Studio as an internal AI platform with models, MCP connections and cost control that you can self-host or use in the cloud. Below are the TypeScript and Bun stack, status badges and plans such as an agent marketplace.