Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Copilot connects Supabase, Box, Calendly and more

Written November 19, 2026

Copilot can now connect Supabase, Box, Calendly, Buildkite, ClickUp, Mixpanel, Webflow and Wix through GitHub-verified MCP servers, in public preview.

A Copilot user whose work lives in Supabase, Buildkite or Calendly had no first-party way to bring that context into a Copilot session: the session could write code, but the schema, the failing build and the meeting schedule sat in other tools. The GitHub Changelog post of November 18, 2026 adds eight more services that connect to Copilot using GitHub-verified MCP servers, or connectors, in public preview. They join more than 25 services that can already connect, such as Slack, Figma, and Sentry. Connect a service once, the post says, and it can be used across Copilot.

The eight new services

The post lists the eight with what each one is for:

The full list of supported connectors is longer than this page. The post points readers to Customize in the Copilot app, or to the Copilot customization page on github.com, to see everything that can connect.

What a connection buys in a session

The post's own examples show the shape of the change. A developer can ask Copilot why the latest Buildkite build failed and have it fix the code in the same session, instead of copying an error out of one tool and into another. Or Copilot can check a Supabase schema before it writes a migration, so the migration is written against the database as it actually stands rather than as the developer remembers it. In both cases the point is the same: the service's context arrives inside the session where the code changes, and the person stops acting as the courier between the two.

That is also the limit of what the post promises. It names, for each service, what that service connects for, and it does not go deeper into per-service behaviour. Anyone planning around a specific connector should read its entry in the supported list the post links, not assume the eight all behave alike.

The four places to connect

These services connect the same way as any other connector, and the post names four places to do it:

The CLI route is the one terminal-first users will reach for. It sits in the same CLI surface that gained Microsoft Entra sign-in a day earlier, covered in Copilot CLI signs in with Microsoft Entra.

The admin policies that can block a connection

Connectors are in public preview for all Copilot plans, but on two plans the individual is not the only person involved. With Copilot Business or Copilot Enterprise, the post says an admin needs to enable the Editor preview features policy before these connectors can be used. A user who cannot see a connector on one of those plans may be looking at a policy that was never switched on, not at a missing feature.

A second gate sits in the enterprise's MCP allowlist. If that allowlist names connectors individually rather than using a wildcard, an admin also needs to add the new connectors to it. An enterprise that allowed the earlier services one by one does not gain these eight automatically: each new connector is a new allowlist entry until someone adds it.

The third gate is on the service's own side. Some services also need to be enabled by an admin there, such as allowing Box MCP access. So a blocked connection can have three different owners — the Copilot plan's preview policy, the enterprise allowlist, or the connected service itself — and the fix differs for each. Checking them in that order saves the round of guessing that starts when a Connect button does nothing.

Related playbooks

Sources

Back to: Coding tasks playbooks hub · Also: Copilot CLI signs in with Microsoft Entra