mirror of
https://github.com/github/awesome-copilot.git
synced 2026-07-17 03:13:25 +00:00
docs: update Learning Hub for Copilot CLI v1.0.63–v1.0.64 changes (#2107)
- understanding-mcp-servers: add deferTools config option (v1.0.63), update /mcp install section to reflect new /mcp registry command (v1.0.64) - agents-and-subagents: update rubber-duck agent section to reflect /subagents configuration and complementary model strategy (v1.0.64) - creating-effective-skills: add argument-hint frontmatter field (v1.0.64) - copilot-configuration-basics: add model family aliases (opus/sonnet/haiku/ gpt/gemini) and /branch alias for /fork (v1.0.64) - automating-with-hooks: add fix note for postToolUse pipe-separated matchers (v1.0.63) 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:
committed by
GitHub
parent
d93a56782e
commit
e737a33955
@@ -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-05-07
|
||||
lastUpdated: 2026-06-23
|
||||
estimatedReadingTime: '8 minutes'
|
||||
tags:
|
||||
- mcp
|
||||
@@ -93,15 +93,15 @@ 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:
|
||||
GitHub Copilot CLI provides a registry-based install flow that lets you browse and install MCP servers with guided configuration — no manual JSON editing required. In v1.0.64+, use the `/mcp registry` sub-command to browse available servers:
|
||||
|
||||
```
|
||||
/mcp install
|
||||
/mcp registry
|
||||
```
|
||||
|
||||
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:
|
||||
You can also install a specific server by name directly:
|
||||
|
||||
```
|
||||
/mcp install @modelcontextprotocol/server-postgres
|
||||
@@ -119,6 +119,8 @@ This guided flow is the recommended way to add new MCP servers, especially for s
|
||||
|
||||
**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.
|
||||
|
||||
**deferTools** *(optional, v1.0.63+)*: When set to `false`, the server's tools are always available even when tool search is enabled. By default, tool search can hide rarely-used MCP tools to reduce context noise; setting `deferTools: false` on a server prevents its tools from being deferred, keeping them permanently in the tool list.
|
||||
|
||||
### 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.
|
||||
|
||||
Reference in New Issue
Block a user