Infrastructure source-of-truth for local MCP-facing services, generated Caddy routing, and deterministic smoke tests.
infra-mcp defines how local MCP and Ollama-facing infrastructure is rendered, deployed, and validated on a node. The repository does not contain the long-running runtime itself; it contains the templates, scripts, contracts, and generated artifacts that make deployment reproducible.
- render Caddy configuration from explicit node metadata
- expose a deterministic local HTTP surface for health and capabilities
- smoke-test the deployed local MCP/Ollama path through the configured Host header
- keep architecture and failure modes explicit before implementation drift happens
templates/: canonical templates for generated runtime artifactsgenerated/: rendered output generated from templates andnode.envmcp/: MCP-side code, currently including discovery toolingscripts/: helper scripts for local startup and deployment supportdeploy.ps1: main deploy pathsmoke-test.ps1: local routing and capability smoke testGOVERNANCE.md: binding architecture contractFAILURE_MODES.md: system-level anti-pattern catalog
Runtime lives outside this repository:
C:\work\tools\mcpC:\work\tools\caddy
This repository remains the source of truth. Deployment is explicit and script-driven.
Create a local node.env from node.env.example.
Required values:
NODE_NAMENODE_FQDNOLLAMA_UPSTREAMMCP_ROOT
The deploy path fails fast if required inputs are missing.
.\deploy.ps1
.\smoke-test.ps1
.\scripts\validate-render.ps1See docs/OPERATIONS.md for the canonical deploy flow, example node.env, and generated-artifact rules.
This repository now has a public baseline with a deterministic render path for both the Caddy config and /.well-known/capabilities.json. The main architecture and governance intent are already present; the next work is mostly incremental hardening around deploy automation and node composition.
See docs/STATUS.md for the current state.