Azure Platform Engineering MCP Server
Provides AI agents with real-time access to live Azure infrastructure, including AKS cluster health, resource management, policy validation, and Terraform analysis through a Model Context Protocol interface.
README
Azure Platform Engineering MCP Server
A Model Context Protocol (MCP) server connected to real Azure infrastructure. Deploys a live AKS cluster and provides AI agents with real-time access to cluster health, Azure resources, policy validation, and Terraform analysis.
No simulated data. Every API call hits live Azure services.
What This Does
This MCP server gives AI agents (Claude Code, GitHub Copilot, etc.) structured access to a real Azure platform:
| Tool | Data Source | What It Returns |
|---|---|---|
check_cluster_health |
Kubernetes API (live AKS) | Real node status, pod health, events, recommendations |
validate_manifest |
PyYAML parser | Policy compliance for real YAML manifests |
analyze_terraform |
HCL analysis | Quality score for Terraform modules |
query_azure_resources |
Azure Resource Manager API | Real resource groups, AKS clusters, VMs |
Architecture

How It Works

Deployment Pipeline

Live Proof
This was deployed and tested against a real AKS cluster on Azure for Students.
kubectl get nodes

kubectl get pods (with real CrashLoopBackOff)

MCP Server Test Output (LIVE)

Azure Portal

Infrastructure
Deployed via Terraform in terraform/main.tf:
| Resource | Details |
|---|---|
| Resource Group | mcp-demo-rg (Sweden Central) |
| AKS Cluster | aks-platform-demo — Kubernetes 1.32 |
| Node Pool | 1x Standard_D2as_v4 (cost-optimised) |
| Network | Azure CNI + Calico network policy |
| Monitoring | Log Analytics workspace + OMS agent |
| Workloads | 3 namespaces: product-api, product-web, platform-monitoring |
The platform-monitoring namespace includes an intentionally failing pod to demonstrate how the health check tool detects and reports real CrashLoopBackOff incidents.
Setup
Prerequisites
- Azure subscription (Azure for Students works)
- Azure CLI (
az) - Terraform
- kubectl
- Python 3.10+
Deploy
# 1. Clone
git clone https://github.com/sat0ps/mcp-server-azure-platform.git
cd mcp-server-azure-platform
# 2. Login to Azure
az login
# 3. Deploy infrastructure
cd terraform
terraform init
terraform plan
terraform apply
# 4. Configure kubectl
az aks get-credentials --resource-group mcp-demo-rg --name aks-platform-demo
# 5. Deploy sample workloads
kubectl apply -f workloads.yaml
# 6. Install dependencies
cd ..
pip install -r requirements.txt
# 7. Set subscription ID
export AZURE_SUBSCRIPTION_ID=$(az account show --query id -o tsv)
# 8. Test
python test_tools.py
Tear Down (stop costs)
cd terraform
terraform destroy
Live Test Output
Platform Engineering MCP Server — Live Test Suite
============================================================
Testing against REAL Azure infrastructure
TEST: Initialize
Server: azure-platform-engineering-mcp v1.0.0
PASS
TEST: Check Cluster Health (LIVE)
Source: LIVE — Kubernetes API
Health Score: 100 (healthy)
Nodes: 1/1 ready
Pods: 25 running, 0 pending, 0 failed
Problem pods:
- platform-monitoring/failing-service: 6 restarts (CrashLoopBackOff)
PASS
TEST: Query Azure Resources (LIVE)
Source: LIVE — Azure Resource Manager API
AKS Clusters found: 1
- aks-platform-demo (swedencentral) — K8s 1.32 — Succeeded
Pool: system — Standard_D2as_v4 x1
PASS
ALL TESTS PASSED (Live Azure)
Diagrams
| Diagram | What It Shows |
|---|---|
| Architecture Overview | Full system: agent → MCP → live tools → real Azure |
| MCP Protocol Flow | Real request flow with CrashLoopBackOff detection |
| Deployment Pipeline | terraform apply → kubectl → test → destroy |
| Incident Detection | How MCP found the failing-service pod |
| Policy Validation | YAML validation gate with real PyYAML parsing |
| Agent Configuration | How agents.md + skills + instructions work together |
| Terraform PR Review | AI-driven PR review with quality scoring |
Project Structure
├── mcp_server.py # MCP server (JSON-RPC 2.0 over stdio)
├── tools/
│ ├── kubernetes_live.py # Real K8s API health checks
│ ├── compliance_live.py # Real YAML policy validation
│ ├── terraform_live.py # Terraform HCL analysis
│ ├── azure_resources.py # Real Azure Resource Manager queries
│ └── azure_metrics.py # Azure Monitor metrics (SDK v2 WIP)
├── terraform/
│ ├── main.tf # AKS + monitoring infrastructure
│ └── workloads.yaml # Sample K8s deployments
├── .claude/
│ ├── agents.md # Agent behaviour configuration
│ └── mcp.json # Claude Code MCP config
├── skills/
│ └── SKILL.md # Repeatable agent procedures
├── instructions/
│ ├── terraform-standards.md # Terraform quality standards
│ └── kubernetes-standards.md# K8s deployment requirements
├── scripts/
│ └── setup.sh # Automated deployment script
├── diagrams/ # Architecture diagrams + live screenshots
├── requirements.txt # Python dependencies
└── test_tools.py # Live test suite
Authentication
Uses DefaultAzureCredential — works with az login, managed identity, and service principals. No credentials stored in the repo.
Related
- Microsoft Azure MCP Server — Microsoft's official generic Azure MCP server
- Model Context Protocol — MCP specification
- platform-engineering-mcp-server — Simulated version (design-first approach)
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。