A glowing AI assistant connects cloud apps and workflow tools above a monitor displaying code and automation diagrams.
GitHub has added eight more services to its Copilot connectors. Connectors are GitHub-verified MCP (Model Context Protocol) servers, and they are rolling out in public preview. The GitHub Changelog entry dated November 18, 2026 adds Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix. This isn't a Windows feature. It does matter to Windows-based developers and to the IT admins who control Copilot policy in their tenants.

A glowing AI assistant connects cloud apps and workflow tools above a monitor displaying code and automation diagrams. What was added​

GitHub describes each new connector in one line:

ServiceWhat GitHub says it's for
BoxSearch and manage content, and use Box AI
BuildkiteWork with pipelines and builds
CalendlyManage scheduling and meetings
ClickUpTrack tasks and projects
MixpanelExplore product analytics
SupabaseWork with projects and databases
WebflowManage sites and content
WixManage sites and business tools

GitHub gives two example workflows. In the first, you ask Copilot why your latest Buildkite build failed and have it fix the code in the same session. In the second, Copilot checks your Supabase schema before it writes a migration. Slack, Figma and Sentry stay available as before.

Treat those examples as GitHub's illustrations. The announcement doesn't say which operations each connector exposes. It also doesn't say which actions need confirmation, or how accurate Copilot's proposed fixes will be.

How this fits the connector model​

The October 28, 2026 launch of connectors set the pattern. Before connectors, giving Copilot outside context meant finding an MCP server, setting up a sign-in, and repeating that in every tool. A service you connect in one place now works across the GitHub Copilot app, Copilot CLI, VS Code, Copilot in the cloud, and GitHub Mobile. GitHub handles the MCP server configuration and authentication.

Developers have long been able to wire up some of these services by hand. For Supabase, that meant a hand-written config pointing at the vendor's MCP endpoint. Several community guides describe those manual setups. One of them, for the Copilot coding agent, relies on a repository secret holding a token. The connector approach replaces that per-tool plumbing with a sign-in and an approval step. That is easier. It also means the setup is less visible, which is a reason for admins to pay attention to policy.

How to connect a service​

GitHub lists four entry points:

  1. Copilot app: open Customize and select Connect on the service you want.
  2. Copilot CLI: run /mcp, switch to the Connectors tab, and select Connect.
  3. VS Code: open the Agents window, go to Customizations, and connect the service.
  4. github.com: browse services on the Copilot customization page and select the one you want.

GitHub's documentation adds a detail for the Copilot app. The Customize tab sits in the app sidebar. You select MCP from the dropdown next to the search field, then pick the GitHub verified filter.

Once connected, Copilot can use a connected service's tools when they are relevant to your request, even if you don't name the service. That is convenient. It also means a connected Calendly or Box account is part of what Copilot may draw on in a session, so connect only what you want in play.

Admin checklist for Business and Enterprise​

Connectors are in public preview for all Copilot plans. Business and Enterprise tenants have extra hurdles. Check these before you tell users to try the new services:

  • Editor preview features policy: this must be enabled, because connectors are in preview.
  • MCP servers in Copilot policy: This must be enabled. If MCP servers are disabled, connectors can't be used.
  • Registry restriction: on clients that enforce it, setting Restrict MCP access to registry servers to Registry only blocks connectors. It must be Allow all for connectors to work there.
  • MCP allowlist: if an enterprise lists connectors one by one, the new ones must be added. GitHub's docs say an allowedMcpServers list must include each connector's URL or a wildcard that matches them. A matching deniedMcpServers entry blocks the connector even if the allowlist permits it.
  • The service's own settings: some services must be enabled on their side. GitHub's example for this release is allowing Box MCP access.

The allowlist point is the one most likely to trip people up. Enterprises that allowlisted the original connectors one by one will find the new eight blocked until someone updates the list.

Where connectors don't work yet​

The documentation says connectors work locally and in Copilot sessions on a cloud sandbox, including sessions started on GitHub.com. They are not yet supported in sessions that run on GitHub Actions, such as when you assign an issue to Copilot. If you plan to hand a Buildkite failure to an issue-assigned Copilot run, that path isn't covered yet.

Analysis: the upside and the open questions​

The upside is real. Build failures, schema questions and task context often live outside the repository. Pulling them into the same session as the code cuts down on tab-switching and copy-pasting logs.

The open questions are about control, and the announcement doesn't answer them:

  • Scope of access: GitHub hasn't published a per-connector permission matrix for these eight services. A Supabase connector that can only inspect schemas is a very different risk from one that can run writes.
  • Data exposure: a Box connector means Copilot may see corporate documents. Review your data-governance rules before enabling it widely.
  • Preview status: the docs say the connectors are subject to change.

My view, from general industry experience rather than anything GitHub has said, is to start with low-risk, read-oriented uses. Pilot the connectors with a small group first. Check what each service's own MCP controls let you restrict.

GitHub's docs list the broader supported connector catalog, and GitHub invites feedback in its Community discussion. The retrieved docs page didn't show the eight new services in its table. The dated changelog is the direct evidence for their addition.

Bottom line​

Eight new connectors, one setup flow, and a policy checklist that Business and Enterprise admins will need to work through. For developers, the main benefit is Copilot sessions that can see build, database and task context. For admins, the main job is making sure allowlists, registry settings and vendor-side MCP switches match what they intend to allow.

 

References

  1. Connect Supabase, Box, Calendly, and more to Copilot GitHub Changelog 2026-11-18T22:04:50+00:00
  2. Copilot connectors - GitHub Docs docs.github.com
  3. Connect Supabase, ClickUp, Buildkite, and more to Copilot - GitHub Changelog github.blog