mcp-devops-agent

An MCP server for planning and provisioning infrastructure through chat. Node.js 20+, ESM, TypeScript. Version 2 replaces the v1 MCP schemas.

Stdio is the default. node dist/index.js serve-http runs a remote service for one operator with private bearer authentication. See HTTP setup for HTTPS, persistent state, project access and client requirements.

Current implementation

The planner composes providers by capabilities, persists workload fingerprints, environments, budgets, adapter checksums, dependency steps and safe resource identities. Missing credentials produce setup instructions.

Bundled mutations cover Vercel, Supabase, Cloudflare, prebuilt public GitHub Pages sites, and a Render template for a remote MCP service. The Render template uses a public GHCR image pinned by SHA-256 and one persistent disk. More than thirty catalog manifests supply recommendation leads. Catalog support does not mean executable provisioning support. Additional providers require explicitly installed, checksum-pinned executable adapters. Full cloud-provider coverage and reviewed OpenTofu modules remain in development; see status.

Connect

Run npm ci, npm run build, then npm test. Configure an MCP client:

{
  "mcpServers": {
    "infrastructure": {
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/mcp-devops-agent/dist/index.js"],
      "env": {
        "MCP_DEVOPS_PROJECT_ROOTS": "[\"/absolute/path/to/application\"]"
      }
    }
  }
}

The client must support human form elicitation for mutations. Credentials belong in the process environment or the server working directory .env, never chat:

• VERCEL_TOKEN, VERCEL_TEAM_ID
• SUPABASE_ACCESS_TOKEN
• CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID
• GITHUB_TOKEN for eligible prebuilt public GitHub Pages sites.
• RENDER_API_KEY, RENDER_OWNER_ID, RENDER_MCP_HTTP_TOKEN for the Render template. The last setting is the private bearer token for the hosted service.

Existing accounts need billing, permissions and agreements configured. Project roots constrain local access, not cloud-token permissions.

Chat workflow

1. analyze_project_infra({projectPath}): bounded workload analysis, source fingerprint and environment key names; no code execution or environment values.
2. list_provider_capabilities / discover_providers: distinguish executable adapters from catalog/advisory leads. Network discovery is opt-in.
3. propose_infrastructure_plan({projectPath,constraints,overrides?}): persist a ranked architecture. Scores: fit 40%, reliability 25%, simplicity 20%, cost 15%. Unknown prices stay unknown; alternatives are Pareto candidates.
4. prepare_infrastructure_plan({planId}): prepare ready dependency steps and reserve project budget. Blocked steps report setup requirements.