Clarify built-in MCP servers in Copilot CLI reference by aosama · Pull Request #43372 · github/docs

GitHub Copilot generated this pull request.

fixes #43371

Summary

This pull request updates the Copilot CLI command reference to make the Built-in MCP servers section consistent with the documented behavior of the --disable-builtin-mcps option on the same page.

Before this change, the page said two conflicting things:

  • The Built-in MCP servers table listed github-mcp-server, playwright, fetch, and time.
  • The --disable-builtin-mcps option said the built-in MCP servers are currently github-mcp-server.

This change resolves that inconsistency by keeping only github-mcp-server in the Built-in MCP servers table.

What changed

  • Removed playwright from the Built-in MCP servers table.
  • Removed fetch from the Built-in MCP servers table.
  • Removed time from the Built-in MCP servers table.

Why

The safest documentation change here is to align the table with the more specific option text that already says the current built-in MCP server set is github-mcp-server.

Local verification also supported treating at least some of the removed entries as not built in in this environment:

  • A Playwright-specific runtime check returned Browser automation is unavailable.
  • A time-tool runtime check returned Time tools are unavailable.

Given that evidence, keeping only github-mcp-server is the most conservative fix and removes the page's internal contradiction without making broader product claims.

Prompt summary - submitted by @aosama

Investigated an inconsistency in the Copilot CLI reference about built-in MCP servers, confirmed the conflict in source, compared it against local Copilot CLI behavior, and updated the reference table so it matches the documented --disable-builtin-mcps behavior.