Enterprise Pattern — MCP recommendations

Pattern: Enterprise
Component: mcps.md
Version: 1.1 | Updated: 2026-07-29

---

Purpose

Least-privilege MCP servers for the Enterprise pattern. Keep mcpServers: {} until a human enables stubs after MCP when and how.

Recommended MCPs

MCP	Why for this pattern
GitHub	Change evidence
Slack / Teams	Optional — incident/comms (allowlist)
Jira / Linear	Optional — control tickets
OpenTelemetry	Optional — tenant-aware traces

When to enable for Enterprise

Enable org MCPs only after SoA rows exist. Slack/Jira stay optional; OpenTelemetry is for tenant-aware traces, not chat ops.

Enable rules (this pattern)

1. Enterprise MCP defaults to deny; each server needs an allowlist owner
2. Never commit tokens; map secrets outside git
3. Record allowlist + data class in MODEL_POLICY / SoA before write tools
4. Strip write tools from any server that can touch confidential tenants

Anti-patterns

• Org-wide MCP enablement without a Statement of Applicability row
• Claiming ISO/NIST progress because a logo MCP connector exists
• Cross-tenant retrieval through a shared filesystem MCP root

Checklist

• Enterprise MCPs mapped to env secrets outside git
• Unused servers remain disabled after the enterprise gate
• Injection / tool PEP reviewed if tools can act