Key takeaways
- GitHub added eight Copilot connectors on November 18, 2026, including Supabase, Box and Buildkite.
- Connectors are GitHub-verified MCP servers, in public preview on all Copilot plans.
- On Business and Enterprise plans an admin must enable the Editor preview features policy first.
GitHub added eight more connectors to Copilot on November 18, 2026: Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix. Connectors are MCP servers that GitHub has verified, so Copilot can read and act on data in those services. They are in public preview on all Copilot plans.
The new ones join more than 25 services that were already available, including Slack, Figma and Sentry. For developers, Supabase and Buildkite are the notable additions: a database platform and a CI service can now be connected to the same Copilot session that edits the code. The rest lean toward product and business work: analytics in Mixpanel, tasks in ClickUp, files in Box and websites in Webflow and Wix. MCP, the Model Context Protocol, is the open standard most AI coding tools now use to plug into outside services.
You can connect a service in four places: the Copilot app (Customize, then Connect), the Copilot CLI (run /mcp and open the Connectors tab), Visual Studio Code (the Agents window, under Customizations) and the Copilot customization page on github.com.
On Copilot Business and Enterprise, an admin first has to turn on the "Editor preview features" policy. Companies whose MCP allowlist names each connector, rather than using a wildcard, have to add the new ones by hand, and some services, such as Box, need an admin to allow MCP access on their side too.
GitHub didn't give a date for general availability. For more on keeping Copilot's agents in check, see our guide on how to check Copilot token usage.
