agent-zone-mcp

Infrastructure Knowledge MCP Server

MCP server for Agent Zone — vendor-neutral infrastructure knowledge, K8s validation, and execution templates for AI agents.

Search 200+ articles, validate K8s manifests, get structured playbooks, and discover the right validation path for your infrastructure work. Free, no API key required.

Features

• 200+ infrastructure articles — Kubernetes, networking, observability, CI/CD, disaster recovery, security, multi-region patterns

• 10 MCP tools — search, validate, get templates and playbooks, submit feedback

• K8s manifest validation — 5 built-in policy checks (resource limits, health probes, security, labels, image tags)

• 5 validation paths — from static analysis (~40% detection) to cloud ephemeral (~98%)

• 19 infrastructure templates — searchable by path, tags, and query with download support

• 6 structured playbooks — step-by-step operational guidance filtered by validation path

• Vendor-neutral — not tied to any cloud provider

• Free, no API key — works out of the box

Related MCP server: Agent Identity MCP Server

Quick Start

npx agent-zone-mcp

Claude Code

claude mcp add agent-zone -- npx agent-zone-mcp

Claude Desktop / Cursor / Windsurf

Add to your MCP config:

{
  "mcpServers": {
    "agent-zone": {
      "command": "npx",
      "args": ["-y", "agent-zone-mcp"]
    }
  }
}

Streamable HTTP

For clients that support HTTP transport directly:

https://api.agent-zone.ai/mcp

Tools

Knowledge

Templates & Playbooks

Validation

How It Works

This is a stdio-based MCP server that wraps the Agent Zone REST API. The npm package runs locally and communicates with api.agent-zone.ai over HTTPS. No API key, no account, no local database — just install and use.

A Streamable HTTP endpoint is also available at https://api.agent-zone.ai/mcp for clients that support remote MCP servers directly.

Example: End-to-End Validation Flow

An agent needs to test a Helm chart and has Docker with 8GB RAM:

1. select_validation_path({work_type: "helm-chart", available_resources: ["docker"], resource_specs: {memory_mb: 8192}}) → recommends Path 3 (minikube) with matching templates and the validate-helm-chart playbook

2. list_templates({path: 3, query: "minikube"}) → finds setup templates

3. get_template({id: "local-full~minikube~profiles"}) → gets requirements and setup details

4. get_playbook({id: "validate-helm-chart", path: 3}) → structured steps with commands and success criteria

5. validate({type: "k8s-manifest", content: "apiVersion: apps/v1\nkind: Deployment..."}) → instant policy checks (resource limits, health probes, security, labels)

Validation Paths

Policy Checks

The validate tool checks K8s manifests against 5 policies:

• require-resource-limits — CPU and memory limits on all containers

• require-health-checks — liveness and readiness probes

• no-latest-tag — pinned image tags (no :latest or missing tag)

• no-privileged — no privileged mode, root user, or privilege escalation

• require-labels — standard app.kubernetes.io/name and app.kubernetes.io/version labels

Links

• npm

• Smithery

• Website

• API

• Agent Discovery

License

MIT