Devopness

Created By
Devopnessa year ago
Devopness MCP server for DevOps happiness! Empower AI Agents to deploy apps and infra, to any cloud.
Overview

what is Devopness?

Devopness is a platform that simplifies the management of cloud applications and multi-cloud infrastructure for both AI agents and humans, ensuring secure and productive operations.

how to use Devopness?

To use Devopness, install the MCP server either in Cursor or VS Code, and configure it with your Devopness user credentials to start managing your cloud infrastructure.

key features of Devopness?

  • Simplified role-based access control and permission management.
  • Cost-effective deployment, ensuring no unexpected charges from cloud providers.
  • Full control over AI agents' actions in DevOps and CI/CD workflows.
  • Comprehensive visibility, auditing, and traceability of actions taken by users and agents.

use cases of Devopness?

  1. Managing cloud infrastructure across multiple providers like AWS, Azure, and GCP.
  2. Enabling teams to provision resources securely without overspending.
  3. Facilitating collaboration between AI agents and human developers in software projects.

FAQ from Devopness?

  • What cloud providers does Devopness support?

Devopness supports major cloud providers including AWS, Azure, DigitalOcean, and GCP.

  • Is there a cost associated with using Devopness?

Devopness aims to keep costs low by only deploying infrastructure that teams have permissions for, avoiding unexpected bills.

  • Can I contribute to the Devopness project?

Yes! Contributions are highly encouraged, and you can find the contributing guide in the repository.

Server Config

{
  "mcpServers": {
    "devopness": {
      "url": "https://mcp.devopness.com/mcp/"
    }
  }
}
Project Info
Created At
a year ago
Updated At
9 months ago
Author Name
Devopness
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago