Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-05-15 19:21:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Learning Hub: v1.0.36-v1.0.40 CLI changes (#1588)

Browse Source 
- Add /chronicle command (GA in v1.0.40): session history and file tracking
- Add --max-autopilot-continues flag for autopilot mode configuration
- Add COPILOT_HOME env var and deprecation notice for --config-dir
- Add client_credentials OAuth grant type for headless MCP authentication
- Add Azure DevOps auto-disable GitHub MCP server FAQ entry

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-05-04 11:06:57 +10:00
committed by GitHub
parent c7b2aecb94
commit 1c6ef8dc7e
2 changed files with 38 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/src/content/docs/learning-hub/understanding-mcp-servers.md
+6 -1
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-16
lastUpdated: 2026-05-01
estimatedReadingTime: '8 minutes'
tags:
- mcp
@@ -179,6 +179,7 @@ These are especially useful for plugins and installer scripts that need to self-
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.
- **`client_credentials` grant type**: For fully headless environments where no browser is available and no user interaction is possible (such as server-to-server automation or CI pipelines), MCP servers can authenticate using the OAuth `client_credentials` grant type. This enables machine-to-machine authentication without any browser redirect or device code prompt.
- **Device code flow (RFC 8628)**: When the CLI runs in a **headless or CI environment** where a browser redirect is not possible, it automatically falls back to the device code flow. You'll see a URL and a code to enter on another device to complete authentication.
- **`/mcp auth`**: If a token expires or you need to switch accounts, run `/mcp auth` inside a session. This opens the re-authentication UI for any OAuth-enabled MCP server and supports account switching. You can re-authenticate without restarting the session.
- **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.
@@ -296,6 +297,10 @@ A: MCP servers run with the same permissions as your user account. Follow least-
A: There's no hard limit, but each server is a running process. Configure only the servers you actively use. Most projects use 1–3 servers.
**Q: I'm using an Azure DevOps repository. Will the GitHub MCP server interfere?**
A: No. Copilot CLI automatically detects Azure DevOps repositories and disables the built-in GitHub MCP server for those sessions. This prevents irrelevant GitHub API calls when your project is hosted on Azure DevOps. Other MCP servers you have configured are unaffected.
## Next Steps
- **Build Agents**: [Building Custom Agents](../building-custom-agents/) — Create agents that leverage MCP tools