microsoft/hve-core
Publicmirrored fromhttps://github.com/microsoft/hve-coreAvailable
docs/getting-started/mcp-configuration.md
183lines · modecode
| 1 | --- |
| 2 | title: MCP Server Configuration |
| 3 | description: Optional configuration for Model Context Protocol servers used by HVE-Core agents |
| 4 | sidebar_position: 6 |
| 5 | author: Microsoft |
| 6 | ms.date: 2026-03-10 |
| 7 | ms.topic: how-to |
| 8 | keywords: |
| 9 | - mcp |
| 10 | - configuration |
| 11 | - azure devops |
| 12 | - github |
| 13 | - context7 |
| 14 | estimated_reading_time: 8 |
| 15 | --- |
| 16 | |
| 17 | Some HVE-Core agents use Model Context Protocol (MCP) servers to integrate with external services. MCP configuration is optional; agents that depend on MCP tools indicate when the required server is unavailable. |
| 18 | |
| 19 | > [!TIP] |
| 20 | > The HVE Core installer skill auto-generates MCP configuration with curated servers and guides you through choosing the right installation method (peer clone, submodule, git-ignored, and others). Install the [HVE Core Installer](https://marketplace.visualstudio.com/items?itemName=ise-hve-essentials.hve-installer) extension and ask any agent "help me customize hve-core installation" for guided setup. The sections below cover manual MCP configuration. |
| 21 | |
| 22 | ## Overview |
| 23 | |
| 24 | MCP tools extend GitHub Copilot's capabilities by connecting to external services. HVE-Core references four curated MCP servers. Configure only the servers relevant to your workflow. |
| 25 | |
| 26 | ## Choosing GitHub vs Azure DevOps |
| 27 | |
| 28 | Most teams use one primary platform for repository hosting and work item management: |
| 29 | |
| 30 | | Repository Hosted On | Configure | Do Not Configure | |
| 31 | |-------------------------|-----------------|------------------| |
| 32 | | GitHub | `github` server | `ado` server | |
| 33 | | Azure DevOps | `ado` server | `github` server | |
| 34 | | GitLab, Bitbucket, etc. | Neither | Both | |
| 35 | |
| 36 | Configuring both is unnecessary unless you work across platforms. If you use other Git hosting or work item systems (GitLab, Jira, etc.), configuration differs and is not documented here. |
| 37 | |
| 38 | ## Agent MCP Dependencies |
| 39 | |
| 40 | | Agent | MCP Servers Used | Notes | |
| 41 | |------------------------|--------------------------|---------------------------------| |
| 42 | | ado-prd-to-wit | ado, microsoft-docs | ADO work item creation | |
| 43 | | github-backlog-manager | github | GitHub backlog management | |
| 44 | | task-researcher | context7, microsoft-docs | Documentation lookup (optional) | |
| 45 | | task-planner | context7, microsoft-docs | Documentation lookup (optional) | |
| 46 | | rpi-agent | Varies by subagent | Delegates to specialized agents | |
| 47 | |
| 48 | Agents without MCP dependencies work without any MCP configuration. |
| 49 | |
| 50 | ## Curated MCP Servers |
| 51 | |
| 52 | HVE-Core documents these four MCP servers: |
| 53 | |
| 54 | ### context7 |
| 55 | |
| 56 | Library and SDK documentation lookup. |
| 57 | |
| 58 | | Property | Value | |
| 59 | |----------|-------------------------| |
| 60 | | Type | stdio | |
| 61 | | Package | `@upstash/context7-mcp` | |
| 62 | |
| 63 | ### microsoft-docs |
| 64 | |
| 65 | Microsoft Learn documentation access. |
| 66 | |
| 67 | | Property | Value | |
| 68 | |----------|---------------------------------------| |
| 69 | | Type | http | |
| 70 | | URL | `https://learn.microsoft.com/api/mcp` | |
| 71 | |
| 72 | ### ado (Azure DevOps) |
| 73 | |
| 74 | Azure DevOps work items, pipelines, and repositories. |
| 75 | |
| 76 | | Property | Value | |
| 77 | |----------|---------------------------------------| |
| 78 | | Type | stdio | |
| 79 | | Package | `@azure-devops/mcp` | |
| 80 | | Requires | Organization name, optional tenant ID | |
| 81 | |
| 82 | ### github |
| 83 | |
| 84 | GitHub repository and issue management. |
| 85 | |
| 86 | | Property | Value | |
| 87 | |----------|--------------------------------------| |
| 88 | | Type | http | |
| 89 | | URL | `https://api.githubcopilot.com/mcp/` | |
| 90 | |
| 91 | ## Complete Configuration Template |
| 92 | |
| 93 | Copy this template to `.vscode/mcp.json` in your workspace root. Remove servers you do not need (typically keep either `github` or `ado`, not both). |
| 94 | |
| 95 | ```json |
| 96 | { |
| 97 | "inputs": [ |
| 98 | { |
| 99 | "id": "ado_org", |
| 100 | "type": "promptString", |
| 101 | "description": "Azure DevOps organization name (e.g. 'contoso')", |
| 102 | "default": "" |
| 103 | }, |
| 104 | { |
| 105 | "id": "ado_tenant", |
| 106 | "type": "promptString", |
| 107 | "description": "Azure tenant ID (required for multi-tenant scenarios)", |
| 108 | "default": "" |
| 109 | } |
| 110 | ], |
| 111 | "servers": { |
| 112 | "context7": { |
| 113 | "type": "stdio", |
| 114 | "command": "npx", |
| 115 | "args": ["-y", "@upstash/context7-mcp"] |
| 116 | }, |
| 117 | "microsoft-docs": { |
| 118 | "type": "http", |
| 119 | "url": "https://learn.microsoft.com/api/mcp" |
| 120 | }, |
| 121 | "ado": { |
| 122 | "type": "stdio", |
| 123 | "command": "npx", |
| 124 | "args": ["-y", "@azure-devops/mcp", "${input:ado_org}", "--tenant", "${input:ado_tenant}", "-d", "core", "work", "work-items", "search", "repositories", "pipelines"] |
| 125 | }, |
| 126 | "github": { |
| 127 | "type": "http", |
| 128 | "url": "https://api.githubcopilot.com/mcp/" |
| 129 | } |
| 130 | } |
| 131 | } |
| 132 | ``` |
| 133 | |
| 134 | ## Method-Specific Notes |
| 135 | |
| 136 | ### Extension Users |
| 137 | |
| 138 | The VS Code extension provides agents without MCP configuration. Create `.vscode/mcp.json` in your project directory if you want to use MCP-dependent features. |
| 139 | |
| 140 | ### Peer Clone / Submodule / Git-Ignored Users |
| 141 | |
| 142 | Create `.vscode/mcp.json` in your workspace root (not inside the hve-core folder). VS Code reads MCP configuration only from the workspace root. |
| 143 | |
| 144 | ### Codespaces / Devcontainer Users |
| 145 | |
| 146 | Create `.vscode/mcp.json` in your repository's `.vscode/` folder. The file will be available inside the container at the workspace root. |
| 147 | |
| 148 | ### Multi-Root Workspace Users |
| 149 | |
| 150 | MCP configuration can be placed in the `.code-workspace` file under `settings` or in the `.vscode/mcp.json` of the primary workspace folder. Workspace-level settings in the `.code-workspace` file take precedence. |
| 151 | |
| 152 | ## Troubleshooting |
| 153 | |
| 154 | ### Agent Reports MCP Tool Unavailable |
| 155 | |
| 156 | 1. Verify `.vscode/mcp.json` exists in workspace root |
| 157 | 2. Check MCP server is running: View → Extensions → MCP SERVERS section |
| 158 | 3. Trust the server when prompted by VS Code |
| 159 | |
| 160 | ### Authentication Errors |
| 161 | |
| 162 | * GitHub: Uses VS Code's built-in GitHub authentication |
| 163 | * ADO: Verify organization name and tenant ID are correct |
| 164 | |
| 165 | ### MCP Server Not Starting |
| 166 | |
| 167 | 1. Ensure Node.js is installed and `npx` is available |
| 168 | 2. Check the Output panel (View → Output → MCP Servers) for error messages |
| 169 | 3. Verify network access to external URLs |
| 170 | |
| 171 | ## References |
| 172 | |
| 173 | * [VS Code MCP Documentation](https://code.visualstudio.com/docs/copilot/customization/mcp-servers) |
| 174 | * [GitHub MCP Server](https://github.com/github/github-mcp-server) |
| 175 | * [Azure DevOps MCP Server](https://learn.microsoft.com/azure/devops/mcp-server/mcp-server-overview?view=azure-devops) |
| 176 | * [Microsoft Learn MCP Server](https://github.com/microsoftdocs/mcp) |
| 177 | |
| 178 | --- |
| 179 | |
| 180 | <!-- markdownlint-disable MD036 --> |
| 181 | *🤖 Crafted with precision by ✨Copilot following brilliant human instruction, |
| 182 | then carefully refined by our team of discerning human reviewers.* |
| 183 | <!-- markdownlint-enable MD036 --> |
| 184 | |