-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[bot] Add /ask, /env, MCP registry install, and plugin marketplace update commands #80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
1b700b4
5089e24
49be6d3
18a1ce0
78e4ace
879d4c6
d1c40ac
9fcf068
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -119,13 +119,29 @@ MCP makes Copilot aware of your actual development environment. | |
|
|
||
| <img src="images/configuring-mcp-servers.png" alt="Hands adjusting knobs and sliders on a professional audio mixing board representing MCP server configuration" width="800"/> | ||
|
|
||
| Now that you've seen MCP in action, let's set up additional servers. This section covers the configuration file format and how to add new servers. | ||
| Now that you've seen MCP in action, let's set up additional servers. You can add servers in two ways: **from the built-in registry** (easiest — guided setup right in the CLI) or by **editing the config file** manually (more flexible). Start with the registry option if you're not sure which to choose. | ||
|
|
||
| --- | ||
|
|
||
| ## Installing MCP Servers from the Registry | ||
|
|
||
| The CLI has a built-in MCP server registry that lets you discover and install popular servers with a guided setup — no JSON editing required. | ||
|
|
||
| ```bash | ||
| copilot | ||
|
|
||
| > /mcp search | ||
| ``` | ||
|
|
||
| Copilot opens an interactive picker showing available servers. Select one, and the CLI walks you through any required configuration (API keys, paths, etc.) and adds it to your config automatically. | ||
|
Comment on lines
+126
to
+136
|
||
|
|
||
| > 💡 **Why use the registry?** It's the easiest way to get started — you don't need to know the npm package name, command arguments, or JSON structure. The CLI handles all of that for you. | ||
|
|
||
| --- | ||
|
|
||
| ## MCP Configuration File | ||
|
|
||
| MCP servers are configured in `~/.copilot/mcp-config.json` (user-level, applies to all projects) or `.mcp.json` (project-level, placed in the root of your project). | ||
| MCP servers are configured in `~/.copilot/mcp-config.json` (user-level, applies to all projects) or `.mcp.json` (project-level, placed in the root of your project). If you used `/mcp search` above, the CLI already created or updated this file for you, but it's useful to understand the format for customization. | ||
|
|
||
| > ⚠️ **Note**: `.vscode/mcp.json` is no longer supported as an MCP config source. If you have an existing `.vscode/mcp.json`, migrate it to `.mcp.json` in your project root. The CLI will show a migration hint if it detects an old config file. | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This command (
copilot plugin marketplace update) is a terminal subcommand, but it appears immediately after an interactive-session snippet (copilot+> /plugin ...). Add a short note clarifying it should be run from your shell (outside the interactive Copilot prompt), otherwise beginners may try to paste it after>and get an error.