[WIP] Add MCP install instructions to skills#111
[WIP] Add MCP install instructions to skills#111TianqiZhang wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This pull request adds MCP installation instructions to all three skill documentation files to help users who have installed the skills but not the Microsoft Learn MCP Server. The changes ensure agents understand how to guide users through MCP installation when needed.
Changes:
- Added "Prerequisites: Connect to the Microsoft Learn MCP Server" section to all three skill files
- Included remote MCP endpoint URL, sample JSON configuration, and a link to the full installation guide
- Placed the prerequisites section immediately after the title and before main content sections
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| skills/microsoft-skill-creator/SKILL.md | Added prerequisites section with MCP installation instructions after the skill title |
| skills/microsoft-docs/SKILL.md | Added prerequisites section with MCP installation instructions after the skill title |
| skills/microsoft-code-reference/SKILL.md | Added prerequisites section with MCP installation instructions after the skill title |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "microsoft-learn": { | ||
| "type": "http", | ||
| "url": "https://learn.microsoft.com/api/mcp" | ||
| } | ||
| } | ||
| } |
There was a problem hiding this comment.
The JSON configuration format uses "mcpServers" as the top-level key, but the README.md shows "servers" as the standard config format (line 67). This inconsistency could confuse users. Consider using "servers" to match the documented standard, or add a note that different MCP clients may use different configuration keys (e.g., "mcpServers", "servers", etc.).
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "microsoft-learn": { | ||
| "type": "http", | ||
| "url": "https://learn.microsoft.com/api/mcp" | ||
| } | ||
| } | ||
| } | ||
| ``` |
There was a problem hiding this comment.
The JSON configuration format uses "mcpServers" as the top-level key, but the README.md shows "servers" as the standard config format (line 67). This inconsistency could confuse users. Consider using "servers" to match the documented standard, or add a note that different MCP clients may use different configuration keys (e.g., "mcpServers", "servers", etc.).
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "microsoft-learn": { | ||
| "type": "http", | ||
| "url": "https://learn.microsoft.com/api/mcp" | ||
| } | ||
| } | ||
| } | ||
| ``` |
There was a problem hiding this comment.
The JSON configuration format uses "mcpServers" as the top-level key, but the README.md shows "servers" as the standard config format (line 67). This inconsistency could confuse users. Consider using "servers" to match the documented standard, or add a note that different MCP clients may use different configuration keys (e.g., "mcpServers", "servers", etc.).
If user only installed our skills but not our MCP, their agent needs to know how to install our MCP.