GitHub Copilot Adds Eight MCP Connectors in Preview
Eight New Connectors Land in Copilot
GitHub released eight public-preview connectors for Copilot on November 18, 2026, adding support for Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow, and Wix (GitHub Changelog). GitHub classified the update as an improvement rather than a numbered release, and the release notes list no breaking changes (GitHub Changelog). The connectors are GitHub-verified MCP servers, meaning they run on the Model Context Protocol standard rather than bespoke Copilot plugins.
Why This Matters for Builders
For developers and teams already wiring agents into business software, the release matters because it formalizes a growing pattern: Copilot users connect a service once and reuse that connection everywhere Copilot runs, rather than re-authenticating per surface. As GitHub put it in the release notes, "Connect these services once, and you can use them across Copilot" (GitHub Changelog). That single-setup model lowers the integration overhead for agent workflows that touch scheduling (Calendly), task tracking (ClickUp), product analytics (Mixpanel), CI/CD (Buildkite), content management (Box, Webflow, Wix) and backend databases (Supabase) — all documented service capabilities in the release (GitHub Changelog).
What's Supported and Where
Connection setup is documented across the Copilot app, Copilot CLI, VS Code, and github.com, and GitHub's broader connector push says connected services also work in Copilot in the cloud and GitHub Mobile (GitHub Changelog). The eight connectors are available in public preview across all Copilot plans, but Copilot Business and Enterprise administrators must enable the "Editor preview features" policy, and enterprises running an individual MCP allowlist need to add the new connectors manually. Some underlying services may also require admin enablement on their own side.
Scale of the Connector Ecosystem
GitHub says the eight additions join more than 25 services already available through Copilot connectors, underscoring how quickly the MCP-based integration layer has expanded since the connector framework's broader rollout in late October 2026 (GitHub Changelog). No installation or usage figures were disclosed for the new connectors specifically. The release notes also do not specify a license for the connectors or their underlying MCP servers, nor do they name individual maintainers beyond GitHub's own verification of the servers.


