GitHub Copilot Adds 8 Verified Connectors Including Supabase and Mixpanel
GitHub Copilot adds verified MCP connectors for Supabase, Box, Buildkite, Calendly, ClickUp, Mixpanel, Webflow, and Wix with one-click sign-in across the app, CLI, and VS Code.
Takeaways
- GitHub Copilot adds 8 verified MCP connectors in public preview.
- New services: Supabase, Box, Buildkite, Calendly, ClickUp, Mixpanel, Webflow, Wix.
- Sign in once, use across Copilot app, CLI, VS Code, and github.com.
- Joins 25+ existing connectors including Slack, Figma, and Sentry.
- Available on all plans; Business/Enterprise admins must enable preview policy.
- Browse and connect from the Copilot customization page.
GitHub is rolling out eight verified connectors in public preview for GitHub Copilot: Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow, and Wix. Developers can authorize each service through a sign-in and reuse the connection across Copilot, avoiding manually managed API tokens, local MCP servers, and YAML configuration.
The connectors use Model Context Protocol, an open standard introduced by Anthropic that lets AI clients discover structured tools and request data or actions from external systems. GitHub hosts and verifies these connector servers, while account scopes and vendor policies continue to govern what Copilot can access.
Eight services enter the catalog
| Service | What Copilot can access |
|---|---|
| Box | Content search and management, including Box AI tools. |
| Buildkite | Pipelines, build results, logs, and failure diagnostics. |
| Calendly | Scheduling data and supported calendar actions. |
| ClickUp | Tasks, project status, and related work context. |
| Mixpanel | Product analytics, including funnels and usage data. |
| Supabase | Projects, databases, and schema information. |
| Webflow | Supported site and content-management operations. |
| Wix | Supported site-management data and actions. |
These additions bring Copilot’s connector catalog to more than 25 services, alongside existing integrations such as Slack, Figma, and Sentry.
One sign-in reaches four surfaces
After authorization, the same connection becomes available in the Copilot app, Copilot CLI, VS Code’s agent window, and GitHub.com. That persistence supports multi-step requests without requiring developers to authenticate separately or paste service data into each session.
- Ask Copilot why the latest Buildkite build failed, inspect the logs, and patch the relevant code in the same session.
- Inspect a Supabase schema before drafting a database migration.
- Pull a Mixpanel funnel into a planning session without copying analytics results between tabs.
- Update a ClickUp task after completing related repository work.
Connect from app, CLI, IDE, or web
- Copilot app: Open Customize, find the service, and select Connect.
- Copilot CLI: Run
/mcp, open the Connectors tab, and select Connect. - VS Code: Open the Agents window, choose Customizations, and connect the service.
- GitHub.com: Open the Copilot customization page, browse the available services, and choose a connector.
Preview access has policy gates
The public preview is available across all Copilot plans at no separate charge. Connector activity remains subject to the usage terms and limits of the existing Copilot subscription and the connected service.
Copilot Business and Copilot Enterprise deployments may require several administrative changes before users can connect:
- An administrator must enable the Editor preview features policy.
- Enterprises that list MCP services individually must add each new connector to their allowlist. Wildcard allowlists already cover them.
- Some vendors require a separate administrator setting within their own service. GitHub identifies Box as one example.
Useful reach, defined limits
Connectors suit context gathering and narrowly scoped actions, such as checking a database schema before generating SQL, retrieving build logs during debugging, or reading product analytics while planning a change. These workflows reduce tab switching and keep source data attached to the coding session.
Each vendor defines the tools its connector exposes. Operations outside that tool set still require a custom MCP server or direct API integration, and requests that chain several tool calls can accumulate noticeable latency.
Service permissions determine the connector’s reach. A broadly privileged Box or Supabase account gives Copilot similarly broad access, so teams should review requested scopes, vendor controls, audit logging, and data-handling requirements before connecting production systems.
Distribution is GitHub’s lever
Cursor, Claude, and ChatGPT also offer connector or MCP catalogs. GitHub is competing through its existing reach across terminals, editors, desktop workflows, and GitHub.com, areas where manually maintained MCP configurations can become fragmented.
Teams evaluating these integrations can consult GitHub’s connector reference to confirm availability and setup requirements before granting access to sensitive data.