Last updated: November 22, 2026
GitHub Copilot connectors now cover eight more services: Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix. Connectors are GitHub-verified MCP servers that you connect once and then use in the Copilot app, Copilot CLI, VS Code and github.com. They are in public preview on all Copilot plans.
Contents
- What is new in Copilot connectors
- All supported connector services
- How to connect a service
- Plans, policies and admin setup
- Allowlist rules for enterprises
- Connectors vs self-configured MCP servers
- Workflows and prompt patterns
- Limitations
- Frequently asked questions
What is new in Copilot connectors
GitHub announced the additions on November 18, 2026 in the changelog post Connect Supabase, Box, Calendly, and more to Copilot. The eight new services join “more than 25 services you can already connect, like Slack, Figma, and Sentry.”
According to the Copilot connectors documentation, a connector is a GitHub-verified Model Context Protocol (MCP) server. GitHub handles the server configuration and authentication. You sign in to the service and approve access once, and its tools then work in every supported Copilot surface without repeating setup.
Copilot can also call a connected service’s tools when they are relevant to your request, even if you do not name the service. They are separate from Microsoft 365 Copilot connectors.
| New connector | What Copilot can do with it (per GitHub) |
|---|---|
| Box | Search and manage content, and use Box AI |
| Buildkite | Work with pipelines and builds |
| Calendly | Manage scheduling and meetings |
| ClickUp | Track tasks and projects |
| Mixpanel | Explore product analytics |
| Supabase | Work with projects and databases |
| Webflow | Manage sites and content |
| Wix | Manage sites and business tools |
All supported connector services
The Supported Copilot connectors reference listed 34 services when we checked on November 22, 2026: Airtable, Amplitude, Apify, Atlassian Rovo, Azure Data Explorer, Bitly, Box, Buildkite, Calendly, Canva, ClickUp, Cloudflare, Composio, Figma, Grafana Cloud, LaunchDarkly, Linear, Lucid, Microsoft Learn Docs, Miro, Mixpanel, Neon, Netlify, Notion, Port, Postman, Sentry, Slack, Statsig, Supabase, Vercel, Webflow, Wix and Work IQ.
Each connector has a fixed MCP server URL in the form https://api.github.com/copilot-connectors/api/v1/connectors/<name>/mcp. For example, Supabase uses githubcopilotsupabasemcp and Box uses githubcopilotboxmcp. Admins need these URLs for allowlists.
How to connect a service
GitHub says you connect the new services the same way as any other connector:
- Copilot app: open Customize in the sidebar and select Connect on the service. The docs add that you can choose MCP from the dropdown next to the search field and apply the GitHub verified filter.
- Copilot CLI: run
/mcp, switch to the Connectors tab and select Connect on the service. - VS Code: open the Agents window, go to Customizations and connect the service.
- github.com: browse services on the Copilot customization page at github.com/copilot/customize and select the one you want.
- Sign in and approve access in the service’s own sign-in flow. After that, the connector is available in the other surfaces too.
Once a service is connected, you can also use it with Copilot in the cloud from GitHub Mobile for iOS and Android, or from a mobile browser.
Plans, policies and admin setup
The changelog states that connectors are in public preview for all Copilot plans. GitHub does not list a separate price for connectors. If your organization or enterprise provides your Copilot seat, these settings must allow them:
| Policy or setting | Required value |
|---|---|
| Editor preview features | Enabled, because connectors are in public preview |
| MCP servers in Copilot | Enabled; if MCP servers are off, connectors cannot be used |
| Restrict MCP access to registry servers | Allow all; Registry only blocks connectors on clients that enforce it |
| Enterprise MCP allowlist | Must include each connector URL or a matching wildcard |
| Service-side access | Some services need their own admin step, such as allowing Box MCP access |
Allowlist rules for enterprises
GitHub’s guide to configuring an MCP server allowlist explains that allow and deny lists live in an enterprise managed-settings.json file, usually stored in a .github-private repository or installed on machines through device management. Connectors are remote MCP servers, so you match them with serverUrl entries.
- No allowlist defined: connectors are allowed unless they match a
deniedMcpServersentry. - Allowlist defined: connectors are blocked unless their URL matches an entry.
- Allow all, including future connectors: add
{ "serverUrl": "https://api.github.com/copilot-connectors/api/v1/connectors/*/mcp" }toallowedMcpServers. - Allow only some: list each connector URL individually. In that case the eight new connectors stay blocked until you add them, as the changelog warns.
- Deny wins: deny rules take precedence, so you can pair the wildcard allow entry with specific deny entries.
Keep your other entries, because any MCP server that matches no entry is blocked.
Connectors vs self-configured MCP servers
| Point | Copilot connector | MCP server you configure |
|---|---|---|
| Setup | GitHub handles configuration and sign-in | You define the server command or URL and its credentials |
| Reach | Connect once, use across supported Copilot surfaces | Defined in user or repository settings for the clients that read them |
| Allowlist match | By connector serverUrl |
By name, server URL or command |
| Status | Public preview, subject to change | Depends on the server you choose |
For a service on the supported list, a connector removes most of the setup work. For an internal tool or a service GitHub does not yet verify, you still configure your own MCP server.
Workflows and prompt patterns
- Fix a failing build: GitHub’s own example is to ask Copilot why your latest Buildkite build failed and have it fix the code in the same session. Try: “Check the latest failed Buildkite build for this branch, explain the failure, then fix it.”
- Check the schema first: “Read the current Supabase schema for the orders table before you write this migration.” This matches GitHub’s Supabase example.
- Combine with logs: the docs suggest investigating a failing service by querying logs and metrics in Grafana Cloud.
Limitations
- Preview status: connectors are in public preview and subject to change.
- No Actions-based sessions yet: connectors are not supported when a session runs on GitHub Actions, such as when you assign an issue to Copilot.
- Admin gates: on Business and Enterprise plans, preview, MCP and allowlist policies can each block connectors.
- Service rules still apply: the connected service may require its own admin approval for MCP access.
Related guides on FreeAnswers
- GitHub Copilot team customizations and plugin defaults
- GitHub Copilot browser use with the Chrome extension
- @GitHub in Slack and Microsoft Teams
- Copilot code review adaptive effort and secret detection
- Claude interactive connectors and MCP Apps
- Raycast MCP server guide
Frequently asked questions
What are GitHub Copilot connectors?
Copilot connectors are GitHub-verified MCP servers for outside services such as Slack, Sentry, Supabase and Box. GitHub handles the server configuration and sign-in, so you connect a service once and use its tools across supported Copilot surfaces. They are in public preview.
Which services were added to Copilot connectors in November 2026?
On November 18, 2026, GitHub added eight services: Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix. They join more than 25 existing services, and the supported connectors list showed 34 services when we checked.
How do I connect Supabase to GitHub Copilot?
In the Copilot app, open Customize and select Connect on Supabase. In Copilot CLI, run /mcp, open the Connectors tab and select Connect. In VS Code, use Customizations in the Agents window. On github.com, use the Copilot customization page.
Are Copilot connectors free?
GitHub says connectors are in public preview for all Copilot plans. It does not list a separate charge for connectors. On Copilot Business or Enterprise, an admin must enable the Editor preview features policy first.
How do admins allow or block Copilot connectors?
Connectors are remote MCP servers, so admins use serverUrl entries in the enterprise allowedMcpServers and deniedMcpServers lists. A wildcard entry allows all connectors, including future ones, and deny rules always take precedence over allow rules.
Sources
- GitHub Changelog: Connect Supabase, Box, Calendly, and more to Copilot (November 18, 2026)
- GitHub Docs: Copilot connectors
- GitHub Docs: Supported Copilot connectors
- GitHub Docs: Configuring an MCP server allowlist for your enterprise
Image: GitHub Changelog announcement graphic for the new Copilot connectors, © GitHub, used for editorial purposes from the GitHub Changelog. FreeAnswers is not affiliated with GitHub.