Agent Control via MCP
devsy mcp serve runs a Model Context Protocol server over stdio. MCP clients can use it to list, create, and run commands in workspaces.
devsy mcp serveConfigure your MCP client to run that command. The config format depends on the client. Example:
{
"mcpServers": {
"devsy": {
"command": "devsy",
"args": ["mcp", "serve"]
}
}
}Tools
| Tool | Purpose |
|---|---|
workspace_list | List workspaces with provider, IDE, and source. |
workspace_status | Get the saved workspace configuration. It does not report whether the workspace is running. |
workspace_create | Create and start a workspace. |
workspace_start | Start an existing workspace. |
workspace_stop | Stop a running workspace. |
workspace_delete | Delete a workspace. Accepts force=true. |
workspace_exec | Run a one-shot command in a running workspace. |
provider_list | List configured providers. |
provider_add | Add a provider from a registry name, GitHub URL, or local path. |
provider_delete | Remove a provider. |
provider_use | Set the default provider. |
To check whether a workspace is running, use devsy workspace status <name> --result-format json.
These flags on devsy mcp serve limit workspace_exec: --exec-timeout-default (5m), --exec-timeout-max (30m), and --exec-output-cap (100 KiB per stream). --mcp-max-concurrent-ops (8) limits concurrent exec, create, and start calls.
Agent skill
Devsy also publishes an agent skill that teaches an agent to pick workspaces and providers, run commands, and recover from timeouts. Install it separately from Devsy and the MCP configuration. It needs Node.js for npx.
npx skills add devsy-org/devsy --skill devsyAdd -g to install it for all projects. Add --agent to pick one agent.
Security
The MCP server has the same authority as your local Devsy CLI. A connected client can create and delete workspaces, run any command in them, and add or remove providers. Connect only clients you trust.