The News, Explained

GitHub added eight external services that can connect to Copilot on November 18. The additions bring tools for documents, scheduling, projects and website operations into Copilot’s working context. Connectors are available in public preview on every Copilot plan, with administrator policies applying to organization-provided subscriptions. Source

A connector links an external service’s information and tools to Copilot through a GitHub-verified Model Context Protocol, or MCP, server. Users sign in to the service and approve access; GitHub handles server configuration and authentication. Once connected, a service can be used across supported Copilot surfaces without repeating setup. Source

The additions cover several kinds of work. Box supports content search and management plus Box AI; Calendly covers scheduling and meetings; ClickUp covers tasks and projects. Webflow brings site and content management, while Wix brings sites and business tools. For development and operations, Buildkite connects pipelines and builds, Supabase connects projects and databases, and Mixpanel connects product analytics. Source

GitHub illustrates the change with investigating a failed Buildkite build and fixing code in the same session, or checking the current Supabase database structure before changing it. A build turns code into a form that can run or be deployed; a pipeline links stages such as builds and checks into a workflow. These are GitHub’s examples of using connected information during a task. Source

Setup starts in different places depending on the surface. In the Copilot app, choose a service under Customize. In the command-based Copilot CLI, run /mcp and open the Connectors tab. VS Code uses Customizations in the Agents window, and github.com uses the Copilot customization page. After connecting, the service can also be used with Copilot in the cloud through GitHub Mobile or a mobile browser. Source Source

Session location also matters. Connectors work locally and in cloud sandbox sessions: cloud environments that run tasks, including sessions started on GitHub.com. Sessions running on GitHub Actions are not yet supported. Assigning an issue to Copilot is an example of that unsupported session path. Source

For an organization-provided subscription, both Editor preview features and MCP servers in Copilot must be enabled. On clients that enforce the registry restriction policy, Registry only blocks connectors; using them requires Allow all. A registry is a catalog of servers the organization can make available. Source

An enterprise MCP allowlist separately controls which servers can be used. On clients that enforce it, a new connector’s address must match an individual entry or a wildcard, which matches a pattern covering multiple server addresses. A matching deny rule blocks a connector even when an allowlist permits it. If multiple managed settings apply, the connector must satisfy every applicable allowlist. The external service may also require administrator approval, such as enabling Box MCP access. Source Source

OYOPICK’s Take

We see value in connecting working context across tools, beyond the number of services added. Someone managing documents, tasks and a website could gain more ways to continue work if an approved connection follows them across Copilot surfaces. What they can actually do depends on the service’s tools and the organization’s permissions. Public preview support can also change. Source

For organizations assessing the announcement, we would consider the plan, session type and administrators’ settings on both sides as one access path. Availability on every plan alone gives an incomplete picture of access for a company account. We hope connection screens make it clearer whether a block comes from a Copilot policy or approval in the external service. Clearer explanations could help users request the access they need and administrators decide its scope. Source Source Source