Suga now has an MCP server. Connect an agent like Claude Code or Cursor to your account and it can do most of what you'd do in the dashboard, from your editor.
Paste the server URL into your MCP client, approve the OAuth consent screen, and pick which orgs the agent can reach. From there it can:
- Build out an environment: containers, volumes, gateways, env vars, secret slots, custom domains, and scaling.
- Inspect a running environment: deploy status, logs and events, endpoints, and capacity.
- Make day-to-day changes: bump an image tag, rotate a secret, add a custom domain.
Changes land in your draft and come back as a deeplink. You review them in the dashboard and click Deploy yourself. Agents can't apply, can't delete a project or environment, and can't read a secret value back out. The connection uses your existing org role, so an agent can't do anything you couldn't.
This replaces the in-app code assistant, which we've retired.
You can look at the full docs here, or get started now.
Claude Code, from your terminal:
claude mcp add --transport http suga https://dashboard.suga.app/api/mcp
Cursor, in ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
{
"mcpServers": {
"suga": {
"url": "https://dashboard.suga.app/api/mcp"
}
}
}
Codex, in ~/.codex/config.toml:
[mcp_servers.suga]
url = "https://dashboard.suga.app/api/mcp"
Then run codex mcp login suga to authenticate.