GitHub Copilot: GitHub-Verified Connectors for Slack, Figma, Sentry and More (Preview)
GitHub CopilotGitHub began rolling out GitHub-verified MCP servers, called connectors, in public preview on all Copilot plans. Developers sign in to a service once and it works across the Copilot app, Copilot CLI, VS Code, Copilot in the cloud and GitHub Mobile, with no server to find or credentials to manage. At launch, 26 services are supported, including Slack, Figma, Notion, Sentry, Linear, Atlassian Rovo, Cloudflare and Vercel.
Key Takeaways
- Connectors replace per-tool MCP setup with a single sign-in that Copilot keeps alive in the background.
- A connection made once is shared across the app, CLI, VS Code, cloud sessions and GitHub Mobile.
- 26 services ship at launch, including Slack, Figma, Notion, Sentry, Linear, Atlassian Rovo, Cloudflare and Vercel.
- In the Copilot app, connected services can be used by scheduled automations for recurring work.
- Business and Enterprise users need an admin to enable the Editor preview features policy first.
- Enterprises with an MCP allowlist must add GitHub-verified servers, and some services need approval on their side.
Connect once, use everywhere
The context a coding agent needs often lives outside the repository: a Slack thread, a Figma design, a Sentry error. Until now, giving Copilot that context meant finding a Model Context Protocol server, setting up a sign-in and repeating the process in every tool. GitHub-verified MCP servers, called connectors, remove that setup. A developer picks a service, signs in and is done. There is no server to find, nothing to install locally and no credentials to manage, and Copilot keeps the connection signed in in the background.
A service connected in one place works across the GitHub Copilot app, Copilot CLI, VS Code, Copilot in the cloud and GitHub Mobile.
26 services at launch
The launch catalog includes Slack, Figma, Notion, Sentry, Linear, Atlassian Rovo, Cloudflare, Vercel and Work IQ, among others. Copilot uses a connected service's tools when they are relevant to the request. In the Copilot app, connectors can also power automations that run on a schedule, so recurring work can pull from those services.
To connect a service:
- Copilot app: open Customize and select Connect on the service.
- Copilot CLI: run /mcp, switch to the Connectors tab and select Connect.
- VS Code: open the Agents window, go to Customizations and connect the service.
- github.com: browse services on the Copilot customization page.
Connectors in the cloud
Connected services also work in Copilot in the cloud, whether a session starts on github.com or in the GitHub Mobile app.
Availability and admin requirements
Connectors are rolling out in public preview to users on all Copilot plans. For Copilot Business or Enterprise, an admin must enable the Editor preview features policy for the organization or enterprise. If an enterprise uses an MCP allowlist in managed settings, an admin must also add GitHub-verified MCP servers to it, and some services must be enabled on their own side, such as allowing Slack MCP access.