Planner Pattern — MCP recommendations

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

---

Purpose

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

Recommended MCPs

MCP	Why for this pattern
GitHub	Issues/PRs for plan evidence
Filesystem	Read scoped roots for context packs
Linear / Jira	Optional — ticket linkage (enable after allowlist)

When to enable for Planner

Turn on GitHub/Filesystem only when ticket history or scoped tree reads are required to finish the plan. Ticket MCPs stay off until allowlisted.

Enable rules (this pattern)

1. Keep planning MCPs read-only until the human approval footer is signed
2. Never commit tokens; map secrets outside git
3. Record allowlist + data class in MODEL_POLICY / SoA before write tools
4. Disable ticket write tools before any coder agent starts

Anti-patterns

• Using MCP issue text as a substitute for locked acceptance criteria
• Leaving Linear/Jira write scopes enabled after the plan gate
• Pulling confidential ticket attachments into the planner context without data-class review

Checklist

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