LABSCO SUMMARY
The agent gets a Devopness role, not your cloud keys.
That is the whole argument. An agent that can create servers needs credentials for the cloud it creates them on, and handing those to a model is a decision most teams will not make. Here the credentials live in Devopness and the agent authenticates as a Devopness user, whose permissions are already scoped per environment — the same scoping you would give a junior engineer. Provisioning from nothing is the other differentiator: this creates the server rather than assuming you already have one to SSH into.
What it is
Devopness's hosted MCP server. Devopness sits between you and AWS, Azure, GCP, DigitalOcean or Hetzner: it provisions servers in accounts you control and deploys onto them. Connecting an agent to Devopness gives it one interface across all of those, rather than one integration per cloud.
What you get
- The account structure itself — organizations, projects, environments, teams, roles and users
- Provisioning: servers created from scratch on the supported clouds, with credentials, SSH keys and SSL certificates managed alongside them
- Deployment: applications, pipelines, files, environment variables, webhooks and virtual hosts, with zero-downtime deploys triggered from a git push
- What runs on the box — services, daemons and cron jobs
- Networking — networks, network rules and subnets
- Actions, which is where you read back what a deploy or a provision actually did
- Role-based permissions per environment, so a teammate can deploy without holding cloud-console access
- Install guides for Cursor, VS Code, Claude Code, Codex CLI, Gemini CLI, Windsurf, Zed, Warp, JetBrains AI, Trae, AntiGravity and OpenCode
Requirements
A Devopness account — free to create — and a cloud provider account for Devopness to provision into. The server is remote, at https://mcp.devopness.com/mcp/, and authenticates two ways: OAuth 2.0 through the browser, which is what most clients will do, or a personal access token sent as a bearer header for clients that cannot run the browser flow. Your cloud credentials stay in Devopness; the agent never holds them.
Setup effort
One command — claude mcp add --transport http devopness https://mcp.devopness.com/mcp/
USE CASES
01
Standing up an environment from nothing
Provision the server on your cloud of choice and deploy the application onto it, in one conversation.
02
Moving an app between clouds
Describe the migration and let the same interface provision on the new provider and redeploy.
03
Finding out why a deploy failed
Read the action that ran and what it reported, without opening a dashboard.
04
Auditing what is running
List the servers in an environment and the services, daemons and cron jobs on them.
05
Catching a certificate before it expires
Check the SSL certificates across environments and renew the ones running out.
06
Letting a teammate deploy without cloud access
Give them a Devopness role scoped to one environment, and let their agent use it.
BEFORE YOU INSTALL
What to know first
Requires
- An active Devopness account (free to create at https://app.devopness.com/)
- A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Server setup
Setup
Create a free Devopness account at https://app.devopness.com/
TERMINAL
claude mcp add --transport http devopness https://mcp.devopness.com/mcp/Start Claude Code:
TERMINAL
claudeInside the Claude Code session, type /mcp to open the MCP management interface
Select the devopness server from the list and choose Authenticate
Review the requested permissions in the browser and click Authorize
Verify with /mcp — Status: connected, Auth: authenticated
Hosted endpoint
ENDPOINT URL
https://mcp.devopness.com/mcp/Add this hosted endpoint to your MCP client, then sign in.
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http devopness https://mcp.devopness.com/mcp/Cursor
CURSOR · URL
https://cursor.com/en/install-mcp?name=devopness&config=eyJ1cmwiOiJodHRwczovL21jcC5kZXZvcG5lc3MuY29tL21jcC8ifQ==VS Code
VS CODE · JSON
{
"servers": {
"devopness": {
"type": "http",
"url": "https://mcp.devopness.com/mcp/"
}
}
}