October 28 catch-up
GitHub announced a public preview of GitHub-verified MCP connectors across Copilot plans on October 28, listing 26 launch services such as Slack, Figma, and Sentry. MCP is a way for AI tools to use another service’s tools and context. Users sign in and approve access once, while GitHub handles the server setup and authentication across supported Copilot surfaces. [1]
A cloud session is not always the same environment
The documented surfaces include the Copilot app, CLI, VS Code, and cloud sessions, with connected services also available through supported mobile cloud sessions. The guide draws a specific boundary: local and cloud-sandbox sessions work, but GitHub Actions sessions, including issue-assigned Copilot runs, are not supported yet. Existing news about Agentic Workflows in Actions does not remove that exception. [1][2]
Check the policies and the external service
Managed use needs both Editor preview features and MCP-server policies to permit it. Registry-only restrictions can block connectors on clients that enforce that policy. Managed allowlists must match the connector URL, and a matching denied-server entry still blocks access. The external service may require its own admin approval. Preview access and policy enforcement vary by client. [2]
Copilot may use a connected service’s tools when they are relevant, even if the prompt does not name that service. GitHub verification does not replace the user’s access approval or an organization’s rules. [2]
Our take
Test one approved service in the exact session type your team plans to use. Review the requested tools, data access, and action permissions before connecting it. If policy blocks the preview, work through the specific restriction with the administrator; convenience alone is not a reason to broadly relax a company policy.
We reviewed public sources and did not connect or test any service.