docs(mcp): add Microsoft Learn MCP server and fix config paths#11
docs(mcp): add Microsoft Learn MCP server and fix config paths#11
Conversation
- Add Microsoft Learn MCP server section with /plugin install workflow - Fix project-level config path from .copilot/mcp-config.json to .vscode/mcp.json - Reorder custom MCP server section after web_fetch - Fix bullet list formatting for Context7 feature highlights Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates the MCP Servers chapter (Chapter 06) to expand optional server guidance and correct where readers should place MCP configuration files.
Changes:
- Corrects the project-level MCP config location to
.vscode/mcp.jsonand clarifies user-level vs project-level scope. - Adds a new “Microsoft Learn MCP Server” section with
/plugin install microsoftdocs/mcpinstallation guidance and usage example. - Improves formatting/flow by converting Context7 feature checkmarks into a bullet list and moving the custom server section after
web_fetch.
Comments suppressed due to low confidence (1)
06-mcp-servers/README.md:336
- This line suggests saving the same JSON either as
~/.copilot/mcp-config.jsonor.vscode/mcp.json, but the surrounding text calls the example “mcp-config.json”. Consider adjusting the wording around this section so readers understand the JSON is identical but the filename differs (mcp-config.jsonvsmcp.json) depending on location.
Save this as `~/.copilot/mcp-config.json` for global access or `.vscode/mcp.json` for project-specific configuration.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## MCP Configuration File | ||
|
|
||
| MCP servers are configured in `~/.copilot/mcp-config.json` (global) or `.copilot/mcp-config.json` (project). | ||
| MCP servers are configured in `~/.copilot/mcp-config.json` (user-level, applies to all projects) or `.vscode/mcp.json` (project-level, applies to just the current workspace). |
There was a problem hiding this comment.
This introduces .vscode/mcp.json as the project-level config, but several later sections still instruct readers to only edit/create ~/.copilot/mcp-config.json. To avoid confusing users, update the nearby instructions (e.g., “Add this to your … and restart”) to mention the project-level file option as well and keep file naming consistent between “mcp-config.json” vs “mcp.json”.
This issue also appears on line 336 of the same file.
| MCP servers are configured in `~/.copilot/mcp-config.json` (user-level, applies to all projects) or `.vscode/mcp.json` (project-level, applies to just the current workspace). | |
| MCP servers are configured in an MCP configuration file, either `~/.copilot/mcp-config.json` (user-level, applies to all projects) or `.vscode/mcp.json` (project-level, applies to just the current workspace). Throughout this chapter, references to “your MCP config file” or “MCP configuration file” mean whichever of these two locations you choose to use. |
|
|
||
| > Look up information about "1984" using the book lookup server | ||
| > Search for books by George Orwell | ||
| > Look up information about "1984" using the book lookup server. Search for books by George Orwell |
There was a problem hiding this comment.
The custom MCP server example combines two separate prompts into a single > line, which is inconsistent with the rest of the page’s CLI examples and reads like one long instruction. Split this back into two prompt lines (each starting with >) or explicitly explain that this is a single multi-part prompt.
| > Look up information about "1984" using the book lookup server. Search for books by George Orwell | |
| > Look up information about "1984" using the book lookup server. | |
| > Search for books by George Orwell. |
Summary
Updates Chapter 06 (MCP Servers) with new content and fixes.
Changes
/plugin install microsoftdocs/mcpworkflow, installed skills, and usage example.copilot/mcp-config.jsonto.vscode/mcp.jsonweb_fetchfor better flow