GitHub has expanded the Copilot connector catalog in public preview, adding eight SaaS services that can be linked to a Copilot session.
Engineers can now query and act on data from Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix without leaving the Copilot interface, which reduces context‑switching and opens new automation possibilities for CI/CD, scheduling, analytics and content management.
New connector lineup
- Box – search, manage content, and invoke Box AI.
- Buildkite – inspect pipelines and builds.
- Calendly – retrieve and modify meeting schedules.
- ClickUp – list tasks and project details.
- Mixpanel – query product‑analytics data.
- Supabase – examine projects and database schemas.
- Webflow – control site content.
- Wix – manage site and business tools.
How to enable Copilot connectors
Connectors are available to every Copilot plan in public preview. For Business or Enterprise plans an administrator must turn on the “Editor preview features” policy. If the organization’s MCP allowlist enumerates connectors individually, the admin must add the new entries. Some services, such as Box, also require the service‑side admin to grant MCP access.
Connection methods are consistent across interfaces:
- Copilot app – open Customize and click Connect next to the desired service.
- Copilot CLI – run
/mcp, switch to the Connectors tab, then select Connect for the target. - VS Code – open the Agents window, go to Customizations, and press Connect on the service.
- GitHub.com – browse the Copilot customization page and choose the service to connect.
Operational and security considerations
Because connectors rely on GitHub‑verified MCP servers, the primary control point is the organization’s MCP allowlist and the “Editor preview features” policy. Adding a connector may require updating the allowlist, which is a change to the inbound authorization surface. Services that need a side‑admin enable (e.g., Box) introduce an additional outbound trust relationship that must be verified.
All connectors remain in public preview, so stability guarantees are limited. Teams should treat them as optional enhancements and monitor GitHub release notes for any changes to preview status or required configuration.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
Practitioners can start experimenting with the eight new connectors to streamline workflows that involve CI/CD, scheduling, analytics or content management. Before rolling out, verify that admin policies and MCP allowlists are updated, and confirm any service‑side permissions. Track usage and feedback through the community discussion to influence the transition from preview to GA.


