Skip to content
important Tools and apps

GitHub Copilot gains eight new MCP connectors in public preview

clearly official source

GitHub has added eight new MCP connectors to Copilot (Supabase, Box, Calendly, Buildkite, and others) in public preview for all Copilot plans. For enterprise plans, administrator approval is required.

GitHub has expanded the range of MCP connectors for Copilot with eight new services, including Supabase, Box, Calendly, and Buildkite. According to GitHub, the connectors are available in public preview for all Copilot plans, and they only need to be connected once, after which they are available across all of Copilot. The connection process works the same way as for existing connectors – via the /mcp command and the Connectors tab.

According to GitHub, this makes it possible, for example, to have Copilot determine why the last build in Buildkite failed and fix the code within the same session, or check the database schema in Supabase before creating a migration. Previously available connectors such as Slack, Figma, or Sentry remain in place.

For the Copilot Business and Copilot Enterprise plans, the new connectors must be enabled by an administrator – by activating the Editor preview features policy, and if necessary also by adding the connectors to the MCP allowlist, if the company uses a list of individual services instead of a wildcard. For some services, such as Box, it is additionally necessary to enable MCP access on the side of that service as well.

What changed

Why it matters

The connectors allow Copilot to work directly with the data and state of external services (databases, CI/CD, meeting scheduling) without having to switch context, which shortens the time needed for common tasks such as fixing a build or designing a migration. For enterprise plans, however, activation requires administrator intervention, so the extension may not reach users automatically.

Two audiences, two different impacts

What this means

01

For individuals

Developers can now work directly within Copilot with the Supabase schema before writing a migration, or identify and fix the cause of a failed build in Buildkite, without leaving the working session.

What to do In Copilot settings, open /mcp, go to the Connectors tab, and connect the needed service (e.g. Supabase or Buildkite).
More practical updates →
02

For a business

Companies using Copilot Business or Enterprise need administrator intervention to activate new connectors – enabling the Editor preview features policy and, if necessary, modifying the MCP allowlist; for some services (e.g. Box), access also needs to be enabled on the side of that service.

Productivity
What to decide If a company uses Copilot Business/Enterprise, check with the administrator whether to enable the Editor preview features policy and, if necessary, add new connectors to the MCP allowlist.
More business impacts →
Box GitHub Copilot integration MCP Supabase developer tools

Check the original

Event sources

clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.

1
GitHub Copilot Changelog primary source · first detected Connect Supabase, Box, Calendly, and more to Copilot