Devopness logo

Devopness

Organization
devopness

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.

Publisherdevopness
Repositorydevopness
LanguageTypeScript
Forks
176
Stars
559
Available tools
0
Transport typestreamable-http
Categories
LicenseApache-2.0
Links
  • Connect tools to AI workflows

    Devopness exposes MCP capabilities that can be used by compatible AI clients and agents.

  • 0 available tools

    Browse the callable actions below, including names and descriptions when provided by the server.

  • Ready-to-copy setup

    Use the installation snippets to configure this server in your preferred MCP client.

  • Open source signals

    559 stars and 176 forks from the linked repository.

Devopness

Deploy apps and provision cloud infrastructure from scratch on AWS, Azure, GCP, DigitalOcean, and Hetzner: in accounts you control.

One platform to replace many tools: Terraform + Ansible + Jenkins + PaaS (Vercel, Heroku, etc), and stack-specific server panels.

Manage apps, Linux servers, and cloud infrastructure from anywhere: web, mobile, API, or natural language in your AI agent through MCP. No SSH or cloud console for routine work.

npm PyPI License: Apache-2.0 Discord GitHub stars

Create free account · Docs · Discord

For AI agents (MCP)

Ask your AI agent to provision servers, deploy apps, migrate between clouds, and manage infrastructure through one MCP server: not a separate integration per cloud or stack.

One-click install

Install Devopness MCP Server in Cursor

Install Devopness MCP Server in VS Code

Example prompt:

Migrate my app from AWS to Hetzner.

AI agent migrating an app from AWS to Hetzner through Devopness MCP

Starting the MCP server prompts you to log in with your Devopness account.

MCP-compatible clients: Cursor, VS Code, Claude Code, Codex CLI, Gemini CLI, Windsurf, Zed, Warp, JetBrains AI, and more. See step-by-step guides in MCP docs.

What Devopness replaces

Many self-hosted deploy tools (Coolify, Dokploy, and similar) assume you already provisioned a server and can connect over SSH. Devopness provisions infrastructure in your cloud from scratch, configures Linux, and deploys your apps. Routine work runs from the web app, API, or MCP: no SSH and no cloud console for everyday tasks.

Devopness combines what teams usually split across multiple tools into one platform:

Cloud infrastructure from scratch

  • Networks, subnets, static IPs, servers, and Linux configuration in your cloud accounts (instead of Terraform, Ansible, and manual cloud console work)

CI/CD and hosted PaaS

  • Deploy pipelines and hosted platforms (instead of Jenkins, GitHub Actions, GitLab CI, Vercel, Heroku, Netlify, Railway, Render, and similar PaaS)

Server and app management panels

Instead of separate panels per stack, use one platform for all stacks. Devopness replaces:

  • PHP: cPanel, Laravel Forge/Envoyer, Plesk, RunCloud, ServerPanel.app
  • Python: FastAPI Cloud, and similar stack-focused tools
  • Ruby: Cloud 66, Hatchbox, Kamal (popular in Rails, works for any stack)
  • Self-hosted (bring your own server): Coolify, Dokploy

What you get

  • Trigger zero-downtime deploys automatically when you push to git
  • See deploy history and infrastructure changes in one place, even from mobile, without SSH or cloud console access
  • Fine-grained, role-based permissions per environment so teammates deploy without direct cloud-console access
  • Run DevOps operations in natural language through MCP when connected to your AI agents

Quick start

  1. Create an account: free, no credit card required
  2. Follow Getting Started: organization -> project -> environment -> first deploy
  3. Connect MCP: optional; one-click in Cursor or VS Code above

For developers, team leads, founders, and agencies shipping on cloud infrastructure they control.

This repository

Open source packages and documentation for Devopness:

PathPackageDescription
/docsDocumentationProduct docs
/packages/sdks/javascript@devopness/sdk-jsJavaScript/TypeScript API SDK
/packages/sdks/pythondevopnessPython API SDK
/packages/ui/react@devopness/ui-reactReact design system
/examples/applicationsExamplesSample app integrations (Rails, Express, Laravel, and more)

Community

Contributing

Contributions are welcome. See CONTRIBUTING.md. If you use AI tools, also read AGENTS.md. All contributions are subject to the Code of Conduct.

Like the project? Star this repo: it helps others discover Devopness.

Release notes: GitHub Releases. Licensed under Apache License 2.0.

Installation

TypingMind
{
  "mcpServers": {
    "devopness": {
      "url": "https://mcp.devopness.com/mcp",
      "env": null
    }
  }
}

Use Devopness MCP with multiple AI models

TypingMind connects MCP tools at the workspace level, so once Devopness is connected, you can use it with different AI models in TypingMind instead of setting it up separately for each model. This MCP connects through a hosted MCP server URL in TypingMind.

Add an MCP server URL

Use this when Devopness is already hosted remotely or your team wants one shared connector that multiple users can access.

1

Open MCP connectors

In TypingMind, go to Plugins, open MCP connectors, then choose Add URL.

  1. Open TypingMind in your browser.
  2. Go to Plugins.
  3. Open MCP connectors.
  4. Click Add URL.
TypingMind Add Custom MCP Server URL form
2

Paste the server URL

Enter https://mcp.devopness.com/mcp in the Server URL field. Add a connection name, description, icon, custom HTTP headers, or OAuth client settings if the server requires them.

  1. Paste https://mcp.devopness.com/mcp into the Server URL field.
  2. Enter a connection name for Devopness.
  3. Add a description and icon if you want it to be easier to identify.
  4. Add custom HTTP headers or OAuth client details if the server requires authentication.
3

Create the connection

Click Create connection, then return to the Plugins list and confirm the new MCP connection is active.

  1. Click Create connection.
  2. Return to the MCP connectors list.
  3. Confirm the Devopness connection appears as active.
  4. Refresh the plugin list if the connection does not appear immediately.
4

Switch models without reconnecting

Start a chat with your preferred model, enable the Devopness tools from Plugins, and switch to another model whenever needed. The MCP connection stays available to the TypingMind workspace.

  1. Start a new chat in TypingMind.
  2. Select the AI model you want to use.
  3. Enable the Devopness tools from Plugins.
  4. Ask the model to use the tool when needed.
  5. Switch to another AI model and reuse the same MCP connection.
TypingMind chat using enabled MCP tools with a selected AI model
Can you use Devopness to help me with this task?
Devopness
Sure. I read it.
Here is what I found using Devopness.

Frequently asked questions

What is the Devopness MCP server used for?

Devopness is an MCP server that lets compatible AI clients connect to external tools and context. In TypingMind, you can add this MCP server once and make its tools available in your AI workspace.

Can I use Devopness MCP with multiple AI models in TypingMind?

Yes. TypingMind connects MCP tools at the workspace level, so you can use Devopness with different AI models such as Claude, ChatGPT, Gemini, or other models you have configured in TypingMind without setting up the MCP server separately for each model.

Why use Devopness MCP with TypingMind?

TypingMind is one of the best frontends for LLM chat because it brings multiple AI models, prompts, plugins, AI agents, API keys, and MCP tools into one workspace. With Devopness connected, you can use its MCP tools across your preferred models while keeping your chat workflow organized in TypingMind.

How do I connect Devopness MCP to TypingMind?

Devopness can be connected in TypingMind by adding its hosted MCP server URL. This is useful when you want a remote MCP connection that is available from your TypingMind workspace.

What tools does Devopness MCP provide in TypingMind?

Devopness exposes MCP capabilities that can be enabled from the TypingMind Plugins page and used in chat or assigned to AI agents.

Do I need to share my API keys with TypingMind to use Devopness MCP?

No. TypingMind is local-first and lets you keep your model providers, API keys, prompts, and MCP configuration under your control. If Devopness requires authentication, add the required headers, OAuth settings, or local configuration for that MCP server when you create the connection.

Related MCP Servers

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇