Hub MCP server
{
"mcpServers": {
"paichart-hub": {
"type": "http",
"url": "https://paichart.app/mcp"
}
}
}{
"mcpServers": {
"paichart-hub": {
"type": "http",
"url": "https://paichart.app/mcp"
}
}
}{
"mcpServers": {
"paichart-hub": {
"type": "http",
"url": "https://paichart.app/mcp"
}
}
}{
"servers": {
"paichart-hub": {
"type": "http",
"url": "https://paichart.app/mcp"
}
}
}{
"mcpServers": {
"paichart-hub": {
"type": "http",
"url": "https://paichart.app/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
pAIchart is an MCP hub for generating reviewed low-level infrastructure designs from high-level requirements. It takes a requirements document and topology specification, then outputs device-specific configurations, validation commands, and rollback procedures across network devices, Terraform, and Kubernetes—coordinating work through a directed acyclic graph of specialist agents that harvest live state, design changes, and apply multi-tier correctness checks before releasing to human approval.
- Convert a high-level requirements document into reviewed, per-device network configurations with proof-of-success commands and rollback plans.
- Generate Terraform and Kubernetes configurations from live cluster and infrastructure state with independent validation using domain-standard tools like Batfish and kubeconform.
- Coordinate multi-domain infrastructure changes where values derived in one domain (like address ranges from network design) flow as constraints into dependent domains (like cloud provisioning).
Tools this server exposes
| Tool | Does |
|---|---|
| PIPELINE | Declare a directed acyclic graph of domain pipelines that harvest live state, design changes, and review results in sequence or parallel, with dependencies pass |
| harvest_live_state | Read-only collection of current device configuration and state from your infrastructure through per-device MCP servers. |
| design | Agent-based generation of infrastructure changes based on high-level requirements and harvested state. |
| author | Translation of designs into vendor-specific configuration syntax for network devices, Terraform, or Kubernetes. |
| review | Multi-tier validation including code-based arithmetic checks (CIDR coverage, ASN authorization), domain-specific validators (Batfish, terraform plan, kubeconfor |
| release_gate | Deterministic approval decision based on all leg approvals, no containment violations, complete coverage, and integration reviewer sign-off. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.