Several HVE-Core agents reference MCP (Model Context Protocol) tools for Azure DevOps, GitHub, Context7, and Microsoft Docs integration. However, none of the 7 installation method docs mention MCP configuration, leaving users without guidance on how to enable these features.

Problem

• Agents like ado-prd-to-wit, github-issue-manager, task-researcher, and task-planner reference MCP tools
• Users installing via any method (Extension, Peer Clone, Codespaces, etc.) have no documentation on MCP setup
• The existing .vscode/README.md has good MCP auth docs but isn't discoverable from installation guides
• Users don't know they should configure either GitHub OR ADO based on their repo hosting (not both)

Proposed Solution

1. Create docs/getting-started/mcp-configuration.md - Central guide with:

   • Overview of MCP as optional enhancement (not required)
   • Table of agents and their MCP dependencies
   • Complete mcp.json template with all 4 curated servers (github, ado, context7, microsoft-docs)
   • Guidance: configure GitHub OR ADO based on repo hosting
   • Note: other Git/work item systems not documented

2. Update each installation method doc with brief MCP section linking to central guide

3. Update hve-core-installer.agent.md to add "Checkpoint 4: MCP Configuration Guidance" after the gitignore checkpoint, ensuring all users see post-installation MCP guidance

Curated MCP Servers

Affected Files

New:

• docs/getting-started/mcp-configuration.md

Updates needed:

• .github/agents/hve-core-installer.agent.md (add Checkpoint 4)
• docs/getting-started/methods/extension.md
• docs/getting-started/methods/codespaces.md
• docs/getting-started/methods/peer-clone.md
• docs/getting-started/methods/submodule.md
• docs/getting-started/methods/git-ignored.md
• docs/getting-started/methods/mounted.md
• docs/getting-started/methods/multi-root.md
• docs/contributing/custom-agents.md

Key Decisions

• MCP is optional, not imposed
• Template only in central guide (not duplicated in method docs)
• Users configure GitHub OR ADO, not both
• Other Git/work item platforms not documented