GitHub Copilot users can now connect eight additional services in public preview, bringing tools for databases, builds and project tracking into their Copilot work. The additions include Supabase, Buildkite and ClickUp, and the connectors support every Copilot plan. For Copilot Business and Copilot Enterprise users, access depends on an administrator enabling the Editor preview features policy.
GitHub says users can ask Copilot to investigate a failed Buildkite build and fix the code during that same session. With Supabase connected, Copilot can inspect a database schema before writing a migration, according to GitHub. The eight additions expand an existing selection of more than 25 connectable services, which already included Slack, Sentry and Figma.
ClickUp gives Copilot access to task and project tracking, while Mixpanel brings product analytics into its supported service connections. Box supports content searches and management as well as access to Box AI. Calendly adds scheduling and meeting management, extending the new group beyond tools for code and databases.
The remaining additions are Webflow, for managing website content and sites, and Wix, for working with sites and business tools. GitHub describes all eight connections as GitHub-verified MCP servers, also called connectors. Once users connect a service, GitHub says they can use that connection across Copilot without connecting it separately in each place.
In the Copilot app, users can find a service under Customize and choose Connect to set it up. Those using Copilot CLI can enter /mcp, move to the Connectors tab and choose Connect for their selected service. GitHub also provides a Copilot customization page where users can browse the supported connections.
For VS Code users, setup starts in the Agents window, with service connections under Customizations. Users working through github.com can select a service from the Copilot customization page to connect it. These routes use the same connection process as Copilot’s other connectors, according to GitHub.
Enterprise users face an additional requirement if their enterprise’s MCP allowlist names individual connectors instead of using a wildcard: an administrator must add the new entries. Permission may also be required from the connected service’s own administrator. GitHub identifies Box MCP access as one example of a setting that may need that separate approval.













