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(learning-hub): add v1.0.40 features — /chronicle GA, COPILOT_HOME, autopilot limit, MCP client_credentials, ACP skills

Browse Source 
- copilot-configuration-basics.md: document /chronicle command (now GA for all users),
  COPILOT_HOME env var (replaces deprecated --config-dir), and
  --max-autopilot-continues flag (default 5 in v1.0.40)
- understanding-mcp-servers.md: add client_credentials OAuth grant type for
  fully headless MCP server authentication (v1.0.40)
- creating-effective-skills.md: note that skills are available as slash
  commands in ACP clients (e.g. Zed) as of v1.0.40

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
github-actions[bot]
2026-05-02 19:44:44 +00:00
committed by GitHub
parent acdae521d2
commit 8b867c8ddd
3 changed files with 26 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
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-16
lastUpdated: 2026-05-02
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` OAuth grant type (v1.0.40+)**: For fully headless environments (e.g., server-side automation, CI pipelines) where a browser redirect is not possible and no human is present, MCP servers can authenticate using the OAuth `client_credentials` grant type. This flow exchanges a client ID and secret for a token without user interaction — no browser, no device code, no manual approval step.
- **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.