docs: update Learning Hub for CLI v1.0.11-v1.0.13 changes (#1229)

- copilot-configuration-basics: add /session rename auto-name feature,
  note that /clear preserves MCP servers in new session
- understanding-mcp-servers: add Authentication section documenting
  OAuth, Microsoft Entra ID (no repeat consent screens), API keys, and
  non-standard Dynamic Client Registration support
- installing-and-using-plugins: note that uninstalling a plugin removes
  its cached data from disk

Sources:
- https://github.com/github/copilot-cli/releases/tag/v1.0.13
- https://github.com/github/copilot-cli/releases/tag/v1.0.12
- https://github.com/github/copilot-cli/releases/tag/v1.0.11

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-03-31 10:51:17 +11:00
committed by GitHub
parent 4a6858179f
commit 235f5740d4
3 changed files with 25 additions and 5 deletions

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-03-27
lastUpdated: 2026-03-30
estimatedReadingTime: '8 minutes'
tags:
- mcp
@@ -139,6 +139,17 @@ Example `.mcp.json` or `.vscode/mcp.json`:
> **Security tip**: Use `${input:variableName}` for sensitive values. VS Code will prompt for these at runtime rather than storing them in the file.
### Authentication
Some MCP servers require authentication to connect to protected resources. GitHub Copilot CLI supports several authentication approaches:
- **OAuth**: MCP servers can use the OAuth flow to authenticate with external services. The CLI handles the browser redirect and token storage automatically. This also works when running in ACP (Agent Coordination Protocol) mode.
- **Microsoft Entra ID (Azure AD)**: MCP servers that authenticate via Microsoft Entra ID are fully supported. Once you complete the initial login, the CLI caches the authentication and **will not show the consent screen on subsequent connections** — you authenticate once per session rather than every time the server reconnects.
- **API keys via environment variables**: Pass secrets through the `env` field in the MCP server configuration (see examples above). Never hardcode credentials in `.mcp.json`.
- **`${input:variableName}` prompts**: VS Code will prompt for these values at runtime, keeping secrets out of committed files.
> **Tip**: If your MCP server uses OAuth with Dynamic Client Registration but hosts its authorization metadata at a non-standard URL (as some enterprise servers like Atlassian Rovo do), Copilot CLI handles this automatically.
## How Agents Use MCP Tools
When an agent declares an MCP server in its `tools` array, Copilot can invoke that server's capabilities during conversation: