Cloud DevOps MCP Server

Cloud DevOps MCP Server

[CI] [npm version] [MCP Registry] [License: MIT] [MCP]

Cloud DevOps MCP Server is a Model Context Protocol v2 server by Alex C. Godwin. It gives MCP clients practical Cloud DevOps tools for infrastructure risk review, incident response, CI/CD readiness and SLO error budget analysis.

The v0.3 line adds cross-domain change correlation on top of evidence-backed analysis. Tools can inspect Terraform plan JSON, AWS IAM policy JSON, Kubernetes YAML and GitHub Actions workflow YAML directly, while assess_cloud_change_bundle connects those findings into one release-risk view with domain summaries, correlated findings and potential change paths.

Table of contents

• Why this exists
• Tools
• Architecture
• Quickstart
• Install from npm
• MCP clients
• Configuration
• Public release verification
• Example tool input
• Demo outputs
• Docker
• Development
• Security model
• Roadmap
• Author

Why this exists

AI assistants are more useful in engineering work when they can call focused tools with clear inputs and consistent outputs. This server provides a Cloud DevOps tool layer for:

• Cross-domain release-risk correlation across infrastructure, identity, runtime and delivery.
• Infrastructure-as-code deployment risk analysis.
• Production incident runbook generation.
• CI/CD delivery readiness review.
• SLO error budget calculations.
• AWS IAM least-privilege review.
• Kubernetes workload production readiness review.
• GitHub Actions workflow security and deployment review.

Tools

Architecture

flowchart TD  Client["MCP client"] --> Transport["stdio transport"]  Transport --> Server["Cloud DevOps MCP server"]  Server --> DomainTools["Domain analyzers"]  DomainTools --> Correlator["Cross-domain correlation engine"]  DomainTools --> Output["Structured guidance"]  Correlator --> Output

Quickstart

Run the published MCP server directly from npm:

npx -y [email protected]

On Windows PowerShell systems where script execution policy blocks npx.ps1, use:

npx.cmd -y [email protected]

Install from npm

Install the CLI globally if you prefer a persistent local command:

npm install -g [email protected]cloud-devops-mcp-server

The package is published on npm as cloud-devops-mcp-server and registered in the official MCP Registry as io.github.alexcgodwin/cloud-devops-mcp-server.

MCP clients

Cloud DevOps MCP Server is designed for MCP clients that support stdio servers, including:

• Cursor
• Claude Desktop
• VS Code with MCP support
• Claude Code
• Other clients that follow the Model Context Protocol stdio transport

Use any MCP host that supports local stdio servers. The server does not require cloud credentials or a hosted endpoint.

Configuration

For MCP clients that support local stdio servers, the recommended public configuration is:

{  "mcpServers": {    "cloud-devops": {      "command": "npx",      "args": ["-y", "[email protected]"]    }  }}

Windows clients can use npx.cmd if npx resolves through a blocked PowerShell wrapper:

{  "mcpServers": {    "cloud-devops": {      "command": "npx.cmd",      "args": ["-y", "[email protected]"]    }  }}

See docs/configuration.md for npm, global-install and source-development configuration options.

Public release verification

The published 0.3.1 package was acceptance-tested from a clean directory using both the npm-installed CLI and the exact public npx command. The test discovered all eight tools, executed all eight successfully through stdio, verified the new cross-domain bundle analysis, rejected malformed input, and found no credential, private-key, token or .env files in the published package. npm also exposes SLSA provenance for the trusted GitHub Actions publish.

See docs/public-acceptance.md for the verification record.

Example tool input

{  "changedResources": ["network", "iam", "kubernetes"],  "includesIamChanges": true,  "includesPublicIngress": true,  "modifiesStatefulResources": false,  "hasRollbackPlan": true,  "hasPeerReview": true,  "hasTerraformPlan": true}

Example output shape:

{  "riskScore": 78,  "riskLevel": "critical",  "changedResources": ["network", "iam", "kubernetes"],  "recommendedReleasePath": "Change-advisory review, maintenance window and staged execution are recommended."}

Demo outputs

See docs/demo.md for practical sample inputs and outputs across the toolset.

Docker

Build and run the server in a container:

docker build -t cloud-devops-mcp-server .docker run --rm -i cloud-devops-mcp-server

Development

npm run devnpm run buildnpm testnpm run check

The core decision logic lives in src/logic.ts and the MCP tool registration lives in src/index.ts.

More project notes are available in DEVELOPMENT.md, RELEASE.md and docs/architecture.md.

Security model

• The server runs locally over stdio.
• It does not require cloud credentials.
• It does not call external APIs.
• It does not write to infrastructure or mutate user systems.
• It returns advisory guidance only; engineers remain responsible for review, approval and execution.

Roadmap

• Expand Terraform plan evidence rules across AWS, Azure and Google Cloud resources.
• Add read-only cloud inventory checks with explicitly scoped credentials.
• Add hosted Streamable HTTP transport with authentication and tenant isolation.
• Add signed release provenance, SBOM generation and automated npm/MCP Registry publication.
• Expand cross-domain correlation with policy packs for identity, data, networking and supply-chain risk.
• Add machine-readable policy profiles for production, staging and regulated workloads.

Author

Built by Alex C. Godwin, Cloud DevOps Engineer.