Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-05-04 22:25:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update Learning Hub with recent Copilot CLI features (v1.0.23-v1.0.30) (#1421)

Browse Source 
- copilot-configuration-basics.md: Add /ask, /env, /statusline commands
  and --mode/--autopilot/--plan startup flags
- automating-with-hooks.md: Document preToolUse modifiedArgs/updatedInput
  and additionalContext fields for modifying tool arguments
- understanding-mcp-servers.md: Add /mcp install registry section and
  note that type field is optional for remote MCP servers
- installing-and-using-plugins.md: Add copilot plugin marketplace update
  command and deprecation notice for repo/URL/path installs
- using-copilot-coding-agent.md: Add Remote Control section
  (replaces steering feature)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
github-actions[bot]
2026-04-20 12:32:57 +10:00
committed by GitHub
parent b360c76848
commit d7cf720ede
5 changed files with 130 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
website/src/content/docs/learning-hub/understanding-mcp-servers.md
View File

@@ -3,7 +3,7 @@ title: 'Understanding MCP Servers'
description: 'Learn how Model Context Protocol servers extend GitHub Copilot with access to external tools, databases, and APIs.'
authors:
- GitHub Copilot Learning Hub Team
lastUpdated: 2026-04-01
lastUpdated: 2026-04-16
estimatedReadingTime: '8 minutes'
tags:
- mcp
@@ -91,6 +91,24 @@ Example `.mcp.json` or `.vscode/mcp.json`:
}
```
### Installing MCP Servers from the Registry
GitHub Copilot CLI can install MCP servers directly from the official registry with guided configuration — no manual JSON editing required. During an interactive session, run:
```
/mcp install
```
A picker will list available servers from the registry. After selecting one, the CLI prompts for any required configuration values (connection strings, API keys, etc.) and writes the completed entry to your persistent MCP config automatically.
You can also install a specific server by name without the picker:
```
/mcp install @modelcontextprotocol/server-postgres
```
This guided flow is the recommended way to add new MCP servers, especially for servers that require multiple configuration values.
### Configuration Fields
**command**: The executable to run the MCP server (e.g., `npx`, `python`, `docker`).
@@ -99,6 +117,8 @@ Example `.mcp.json` or `.vscode/mcp.json`:
**env**: Environment variables passed to the server process. Use these for connection strings, API keys, and configuration—never hardcode secrets in the JSON file.
**type** (remote servers): The transport type for remote MCP servers (`http` or `sse`). This field can now be omitted — the CLI defaults to `http` when no type is specified, simplifying remote server configuration.
### Managing Persistent MCP Configuration via Server RPCs
In addition to file-based configuration, GitHub Copilot CLI exposes **server RPCs** that let MCP servers and tooling scripts manage the persistent MCP server registry at runtime. This enables programmatic setup — for example, an installer script that registers a server without requiring you to hand-edit a JSON file.