mcp-agentic-framework
An MCP-based communication framework enabling multiple AI agents to collaborate through asynchronous messaging, built with TDD and functional programming principles - a clean, tested reference for MCP server design.
View source on GitHubKey takeaways
- 01
Async agent-to-agent messaging over MCP primitives
- 02
TDD applied to MCP servers: tools are testable functions
Flows built on this research
MCP & Tooling
Testing MCP Tools
Bring TDD discipline to MCP servers: unit-test handlers, protocol-test the surface, and contract-test against a real host.
4 steps · 60-90 minutes
MCP & Tooling
Tool Permissioning Tiers
Classify tools by risk and enforce tiered permissions: auto-allow, session-allow, always-ask, and never - enforced in the harness.
4 steps · 60-90 minutes
From the archive
Verbatim excerpts mined from our local archive of this repository — the prompts, schemas, and patterns worth stealing.
Production MCP server deployment with health probes
containers:
- name: mcp-server
image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
ports:
- containerPort: 3113
name: http
resources:
limits: { cpu: 500m, memory: 512Mi }
requests: { cpu: 100m, memory: 256Mi }
livenessProbe:
httpGet: { path: /health, port: 3113 }
initialDelaySeconds: 10
periodSeconds: 30
readinessProbe:
httpGet: { path: /health, port: 3113 }
initialDelaySeconds: 5
periodSeconds: 10 MCP servers as first-class services: a Helm chart treating an agent-communication server like any production workload, with liveness/readiness probes and resource budgets.
charts/mcp-agentic-framework/values.yaml