Verified MCP connectors make agent context portable

The repository is rarely the whole context of a build. The design is in Figma, an incident is in Sentry, a decision is in Slack, and the deployment lives somewhere else. GitHub's verified MCP connectors are an attempt to make that context connection a product setting instead of a repeated setup task.

GitHub says users can connect a verified service once and use it across the Copilot app, CLI, VS Code, cloud sessions, and mobile. The public preview starts with 26 services, including Slack, Figma, Sentry, Linear, Cloudflare, and Vercel.

Portability changes the permission question

One connection across clients is convenient, but it also widens the surface where an agent can call a tool. GitHub says organizations may need preview policies and MCP allowlists, and some services require their own administrator approval. That is not friction to remove blindly; it is part of the trust boundary.

Connect once is a usability feature. Scope once is a governance problem.

Builders should connect the smallest useful set, prefer read-only scopes when available, and test what context the agent can retrieve from every client. A connector is valuable when it removes repetition without turning the entire organization into ambient context.