Log inSubmit server
Devopness logo

Devopness

Provision cloud infrastructure, deploy applications, and manage DevOps across AWS, Azure, GCP, DigitalOcean, and Hetzner.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Devopness

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for devopness, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

The devopness MCP server connects AI agents to Devopness for provisioning cloud infrastructure, deploying applications, managing Linux servers, and running CI/CD operations. It works across AWS, Azure, GCP, DigitalOcean, and Hetzner through a single MCP connection, with Devopness handling access to connected cloud accounts. Reach for it when you want an agent to deploy or migrate applications without separate cloud-specific integrations, SSH sessions, or routine cloud-console work. Authentication starts with a Devopness account login when the MCP connection is initiated.

Use cases

  • Provision servers and networks in a selected cloud
  • Deploy applications from an AI coding client
  • Migrate an application between supported cloud providers
  • Trigger zero-downtime releases
  • Review infrastructure and deployment changes

Key features

  • Multi-cloud provisioning across five providers
  • Application deployment and migration
  • Linux server configuration
  • CI/CD pipelines and hosted platforms
  • Environment-level role-based permissions
  • Natural-language DevOps operations through MCP

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars573Stargazers on the source repository.
Last commit1d agoMost recent push to the default branch.

How Devopness works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Devopness

devopness is an MCP server that connects AI agents to the Devopness platform and cloud accounts on AWS, Azure, GCP, DigitalOcean, and Hetzner. Its main tools support provisioning infrastructure, configuring Linux servers, deploying and migrating applications, managing CI/CD workflows, and reviewing deployment or infrastructure changes.

Install it through the one-click setup for Cursor or VS Code, using Devopness's hosted MCP endpoint. When the connection starts, sign in with a Devopness account. The project also provides MCP guides for Claude Code, Codex CLI, Gemini CLI, Windsurf, Zed, and JetBrains AI.

Yes, devopness works with Cursor through a one-click MCP installation link. The connection uses Devopness's hosted HTTP endpoint, and starting the server prompts you to log in with your Devopness account.

Devopness supports AWS, Azure, GCP, DigitalOcean, and Hetzner. Through the MCP connection, agents can provision infrastructure, deploy applications, and migrate workloads across these supported providers.

Yes, devopness supports routine application deployment and infrastructure management without SSH or direct cloud-console work. Agents can use MCP for operations such as deployments, migrations, and infrastructure changes through the Devopness platform.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDevopness AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/devopness?style=directory)](https://allmcps.com/mcp/devopness)
HTML Embed
<a href="https://allmcps.com/mcp/devopness"><img src="https://allmcps.com/api/badge/devopness?style=directory" alt="Devopness on AllMCPs" /></a>