GitHub · 2026-04-13 · notable
GitHub Copilot CLI v1.0.25 — MCP Registry Integration
GitHub Copilot CLI adds direct MCP server registry installs, remote session control, a /env command, and ACP-client MCP support in an 18-item patch release.
Copilot CLI can now install MCP servers straight from the registry, run remote sessions, and hand MCP to ACP clients.
Key specs
| Version | 1.0.25 |
|---|---|
| GitHub stars | 10k |
| Items shipped | 18 |
What is it?
GitHub Copilot CLI is GitHub's official terminal agent — the same Copilot coding agent, usable interactively from a shell, with session history, slash commands, and full GitHub-auth integration. Version 1.0.25 is an 18-item update in the official github/copilot-cli repo; the repo has 10k stars and 228 total releases since launch.
How does it work?
The headline feature is guided MCP-server installation directly from the MCP registry inside the CLI — you pick a server, the CLI configures it and wires it into the current session. A sibling change lets ACP (Agent Client Protocol) clients supply their own MCP servers over stdio, HTTP, or SSE. Session plumbing also gets tighter: model resolution now persists across resumes, a new /env command dumps loaded environment details, and --remote / /remote flags let you drive an active session from another terminal.
Why does it matter?
MCP has become the lingua franca for giving agents new tools, but installing and configuring servers is still fiddly. Copilot CLI treating the MCP registry as a first-class install target pushes MCP a step closer to 'apt-get for agents' — and because Copilot CLI already ships to anyone with a GitHub login, this change exposes that workflow to a very large audience in a single release.
Who is it for?
Developers who live in the terminal and are trying to standardize on MCP for agent tools.
Try it
gh copilot --help