# devopness [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/devopness/devopness  
**GitHub Stars:** 573  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/devopness

## Description
Devopness: AI DevOps on your cloud. Deploy apps, infra and CI/CD. Any cloud and any stack, one MCP. Deterministic API, opinionated and fully configurable. No cloud credentials in AI chats. Free plan.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What devopness does

The devopness MCP server exposes Devopness operations to AI agents. It lets an agent provision infrastructure from scratch, configure Linux servers, deploy applications, migrate workloads between supported cloud providers, and manage deployment or infrastructure activity through natural-language requests.

Devopness supports AWS, Azure, GCP, DigitalOcean, and Hetzner. Its platform covers networks, subnets, static IP addresses, servers, application deployments, deployment pipelines, hosted platforms, and environment-level permissions. This makes the MCP connection relevant for teams that want one automation surface across multiple clouds or application stacks.

## How it works

The MCP connection routes agent requests through Devopness rather than requiring a separate MCP integration for each cloud or stack. Cloud infrastructure is created in accounts controlled by the user, while Devopness handles the platform-side provisioning and management workflow.

Typical requests include provisioning a server, deploying an application, triggering a zero-downtime deployment, reviewing deployment history, and moving an application from one supported cloud to another. Devopness also supports routine management through its web application, API, and mobile experience, so MCP is one access method within the broader platform.

The service is intended to keep cloud credentials out of AI chat interactions. Fine-grained, role-based permissions can be applied per environment so team members can perform deployments without direct access to a cloud console.

## Setup and configuration

Create a Devopness account to begin; the free plan does not require a credit card. After connecting the MCP server, the login flow prompts you to authenticate with that account. The normal product onboarding path is to create an organization, project, and environment before making the first deployment.

Cursor and VS Code provide one-click installation links. The published MCP configuration uses Devopness's hosted HTTP endpoint at `https://mcp.devopness.com/mcp/`. Step-by-step MCP guides are available for the supported clients listed by the project, including Claude Code, Codex CLI, Gemini CLI, Windsurf, Zed, and JetBrains AI.

## Tools and capabilities

- Provision networks, subnets, static IPs, servers, and Linux configuration.
- Deploy applications and trigger zero-downtime releases.
- Create and manage deployment pipelines and hosted platforms.
- Migrate applications between AWS, Azure, GCP, DigitalOcean, and Hetzner.
- Review deployment history and infrastructure changes.
- Apply role-based permissions at the environment level.

## Limitations and notes

Devopness operates on cloud accounts controlled by the user, so the relevant infrastructure and account access must be available through the Devopness platform. The MCP server is best suited to teams that want Devopness to coordinate infrastructure, application deployment, and CI/CD workflows across supported clouds. The project is licensed under Apache License 2.0.

_Full upstream README: https://allmcps.com/mcp/devopness/readme_