GitHub Copilot adds eight MCP connectors in public preview
Supabase, Box, Buildkite, Calendly, ClickUp, Mixpanel, Webflow and Wix can now be connected to Copilot through GitHub-verified MCP servers.
Eight services join the connector list
On November 18, 2026, GitHub added eight more services to its GitHub Copilot MCP connectors, all built on GitHub-verified MCP servers and all in public preview. The new entries are Supabase, for working with projects and databases; Box, for searching and managing content and using Box AI; Buildkite, for pipelines and builds; Calendly, for scheduling and meetings; ClickUp, for tasks and projects; Mixpanel, for product analytics; Webflow, for sites and content; and Wix, for sites and business tools. GitHub lists all eight in the November 18 changelog post.
Slack, Figma and Sentry stay available as connectors, and GitHub says a service only has to be connected once before it can be used across Copilot.
Where you set a connector up
GitHub describes four places to connect a service, and the steps differ slightly per surface:
- In the Copilot app, open Customize and select Connect on the service.
- In Copilot CLI, run
/mcp, switch to the Connectors tab and select Connect. - In VS Code, open the Agents window, go to Customizations and connect the service.
- On github.com, browse services on the Copilot customization page and pick one.
The post gives two examples of what the connections are for. You can ask Copilot why your most recent Buildkite build failed and have it fix the code in the same session, or have it check your Supabase schema before it writes a migration.
What this likely changes for builders
This suggests a shift in how context reaches the assistant. Rather than pasting a schema dump or a build log into chat, a connected Copilot may be able to read that state from the service itself and act on it without leaving the session. For anyone shipping a web app, the Supabase and Buildkite connectors are the two that touch day to day work most directly: database structure and continuous integration output.
That is inference, not something the post promises. What the source confirms is narrower: the connectors exist, they are in public preview, and the two worked examples above are the ones GitHub chose to show.
Limits and open questions
The post leaves several things unstated. There is no general availability date, no detail on permission scopes or what each connector can read versus write, and no information on rate limits or how data pulled from a service is handled. It also does not say whether the connectors behave identically across the app, CLI, VS Code and github.com.
Availability has conditions. Connectors are in public preview for all Copilot plans, but on Copilot Business or Copilot Enterprise an admin has to enable the Editor preview features policy. If an enterprise MCP allowlist names connectors one by one instead of using a wildcard, an admin also has to add the new ones. Some services need to be switched on from their own side too; GitHub gives Box MCP access as an example. Preview status also means behaviour can change.
What it means for AI-assisted app building
The direction is toward assistants that pull context from the tools a project already runs on instead of relying on whatever a developer remembers to paste. If you are building an app with Draftship, the AI chat works from your project and its data rather than from third-party connectors, and managing your app data covers how that side works. Draftship does not offer these Copilot connectors and is not affiliated with GitHub.
Primary sources
- Connect Supabase, Box, Calendly, and more to Copilot · GitHub Changelog, Nov 18, 2026
This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.