Document model fallback lists, CIMD OAuth, and sandbox network isolation changes (v1.0.83) (#2953)

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-09-07 04:15:10 +00:00
committed by GitHub
co-authored by PretaSOFT Copilot
parent c2e1edf8c9
commit f38fb6cf03
3 changed files with 18 additions and 3 deletions
@@ -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-08-28
lastUpdated: 2026-09-05
estimatedReadingTime: '8 minutes'
tags:
- mcp
@@ -215,6 +215,8 @@ Some MCP servers require authentication to connect to protected resources. GitHu
> **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.
> **Client ID Metadata Document support (v1.0.83+)**: Copilot CLI can now sign in to MCP servers using a **Client ID Metadata Document (CIMD)** for OAuth, an alternative to Dynamic Client Registration where the client's identity is published as a metadata document at a URL instead of being registered ahead of time with the authorization server.
## 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: