GitHub connects Copilot to eight more services, including Supabase and Box
The public preview reaches every Copilot plan. GitHub’s examples pair outside service context with coding work, while workplace access depends on administrator settings.
Loading page…
The public preview reaches every Copilot plan. GitHub’s examples pair outside service context with coding work, while workplace access depends on administrator settings.
Listen to this story
GitHub’s November 18, 2026 public preview makes Copilot sessions a hub for eight third-party MCP connections, spanning databases and build pipelines to analytics, scheduling, project work, and site management. The integrations let Copilot use context from connected services—for example, inspect a Supabase schema before drafting a migration or investigate a failed Buildkite build—without leaving the session. Copilot Business and Enterprise customers still need administrator approval, and individually managed connector allowlists or permissions on the connected service may add setup steps.
The new connectors are Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow, and Wix; they join Slack, Figma, and Sentry.
Users can connect services through the Copilot app, CLI, VS Code, or github.com; a connection then works across supported Copilot interfaces.
Business and Enterprise admins must enable the Editor preview features policy; enterprises that approve connectors individually must also allowlist the additions.
GitHub Copilot can now connect to eight more services, bringing databases, build systems, scheduling and other work tools into its sessions. GitHub introduced the GitHub-verified MCP connectors on November 18, 2026, in public preview across all Copilot plans. Business and Enterprise users need administrator approval through specific policy settings before using them.
The connectors are MCP servers—the connections GitHub offers for working with these services through Copilot. The additions are Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix. They join existing connections to services including Slack, Figma and Sentry.
GitHub illustrates the coding workflow with Buildkite: ask Copilot why the latest build failed, then have it fix the code in the same session. Its Supabase example puts a check before code generation, asking Copilot to inspect the database schema before writing a migration—a change to the database’s structure. These are GitHub’s suggested uses for the connections.
The other connections extend beyond those two coding examples. GitHub lists a different scope for each service, from searching documents to exploring product analytics:
Setup uses Copilot’s existing connector controls rather than a separate process for these eight additions. GitHub provides four entry points, depending on where a user works:
For Copilot Business and Copilot Enterprise, an administrator must enable the Editor preview features policy. Enterprises that approve MCP connectors individually must also add the new connectors to their allowlist. That extra allowlist step applies when connectors are listed one by one, rather than permitted through a wildcard.
Permission may also be needed on the connected service’s side. GitHub points to Box as an example, where an administrator may need to allow MCP access. Once a service is connected, GitHub says that connection can be used across Copilot, without reconnecting it for each supported interface.
Loading discussion...
Join the conversation
Explain where you would still want a human check.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.