Connect your tools to Copilot without all the setup

[ebndev]

The context your agent needs is often outside your repository: a thread in Slack, a design in Figma, an error in Sentry. Until now, giving Copilot that context meant finding a Model Context Protocol (MCP) server, setting up a sign-in, and repeating that in each tool you use. GitHub-verified MCP servers, or connectors, are rolling out in public preview, so you only have to connect once.

Connect once, use it across Copilot

Pick a service, sign in, and you're done. There's no server to find, nothing to install locally, and no credentials to manage. A service you connect in one place works across the GitHub Copilot app, Copilot CLI, VS Code, Copilot Chat on github.com, and GitHub Mobile, with no extra setup. Copilot keeps you signed in in the background.

Bring in the tools your team already uses

At launch, you can connect 26 services, including Slack, Figma, Notion, Sentry, Linear, Atlassian Rovo, Cloudflare, Vercel, and Work IQ.

To connect a service:

• Copilot app: Open Customize and select Connect on the service you want.
• Copilot CLI: Run /mcp, switch to the Connectors tab, and select Connect on the service you want.
• VS Code: Open the Agents window, go to Customizations, and connect the service you want.
• github.com: Browse services on the Copilot customization page and select the service you want.

Copilot uses a connected service's tools when they're relevant to your request. In the Copilot app, you can also set up automations that use a connected service on a schedule, so Copilot does recurring work for you.

Use connected services in cloud agent sessions

Connected services also work in Copilot cloud agent sessions started from Copilot Chat on github.com or the GitHub Mobile app.

Try it

GitHub-verified MCP servers are rolling out in public preview to users on all Copilot plans. To try them with Copilot Business or Copilot Enterprise, an admin needs to enable the Editor preview features policy for your organization or enterprise. If your enterprise uses an MCP allowlist in managed settings, an admin also needs to add GitHub-verified MCP servers to it. Some services also need to be enabled by an admin on their side, such as allowing Slack MCP access.

Learn more about GitHub-verified MCP servers. Share feedback in the comments below!

Happy coding! 💙

Tune in for Day 2 of GitHub Universe & check out our round-up post of releases in the Community that need your input ⏭️