Architecture Pattern — MCP recommendations
Pattern: Architecture
Component: mcps.md
Version: 1.1 | Updated: 2026-07-29
Purpose
Least-privilege MCP servers for the Architecture pattern. Keep mcpServers: {} until a human enables stubs after MCP when and how.
Recommended MCPs
| MCP | Why for this pattern |
|---|---|
| GitHub | ADR PRs |
| Filesystem | Read existing topology docs |
When to enable for Architecture
Filesystem loads existing ADRs/topology docs; GitHub opens the ADR PR. Architecture work does not need cluster write tools.
Enable rules (this pattern)
- Architecture MCP is documentation and history — not infrastructure mutation
- Never commit tokens; map secrets outside git
- Record allowlist + data class in MODEL_POLICY / SoA before write tools
- Close filesystem roots once the ADR draft cites its sources
Anti-patterns
- Inventing topology because MCP could not find the current diagram
- Merging ADRs via tool without the architecture review gate
- Skipping rejected alternatives because search returned one popular blog
Checklist
- Architecture MCPs mapped to env secrets outside git
- Unused servers remain disabled after the architecture gate
- Injection / tool PEP reviewed if tools can act
Version: AIES v1.0.0✏️ Edit this page on GitHub