Coding agentGitHubConfirmed
Story 8 of 18 in the Wednesday 18 November editionGitHub adds eight verified MCP connectors to Copilot in public preview
Rolling out on 18 November 2026 across all Copilot plans for Supabase, Box, Buildkite, Calendly, ClickUp, Mixpanel, Webflow and Wix across IDE, CLI and web.

GitHub rolled out eight new GitHub-verified Model Context Protocol (MCP) server connectors in public preview across all Copilot plans on 18 November 2026, expanding Copilot’s pre-vetted integration catalogue past 33 services alongside Slack, Figma and Sentry, and following GitHub’s Ignite browser and Azure DevOps previews. The new connectors add Supabase for database projects and schemas, Buildkite for CI pipelines and failed builds, Box for content search and Box AI, ClickUp for tasks, Mixpanel for product analytics, Calendly for scheduling, and Webflow and Wix for site management.
Sign-in-once setup across CLI, VS Code, Copilot app and enterprise policies
Instead of hand-editing local MCP JSON server files on each machine, developers connect a service once via OAuth - through Customize in the Copilot app, the /mcp Connectors tab in Copilot CLI, Agents Customizations in Visual Studio Code or the Copilot customisation page on github.com - and reuse that authenticated link across every surface.
In a single coding session, Copilot can inspect why a Buildkite pipeline failed before patching the repository or verify a live Supabase table schema prior to generating a SQL migration. On Copilot Business and Enterprise plans, administrators must enable the Editor preview features policy and add the new servers to any explicit non-wildcard MCP allowlist.
Technical details
- Eight new verified connectors
- Supabase, Buildkite, Box, ClickUp, Mixpanel, Calendly, Webflow and Wix (joining 25+ existing services)
- Supported Copilot surfaces
- GitHub Copilot app, Copilot CLI (/mcp Connectors tab), Visual Studio Code and github.com
- Plan eligibility
- Public preview across all GitHub Copilot plans
- Enterprise admin controls
- Requires Editor preview features policy, explicit MCP allowlist updates and upstream vendor toggles (such as Box MCP)
Release details & context
Third-party admin prerequisites and cross-surface credential sharing
GitHub’s changelog notes that certain external SaaS platforms enforce their own tenant-side gatekeeping on top of GitHub’s Copilot policies: for example, enterprise Box administrators must explicitly permit Box MCP access inside their Box console before team members can complete the Copilot OAuth handshake.
Once authorised on any one client, connector state follows the user’s GitHub identity across desktop, terminal and browser sessions, complementing GitHub’s Copilot app security alerts extension.
Common questions
How do developers connect a GitHub-verified MCP server inside Copilot CLI?
Run /mcp inside Copilot CLI, switch to the Connectors tab, select Connect next to the target service and complete sign-in once to enable it across CLI, VS Code, github.com and the Copilot app.
Sources
GitHub release timeline (6 launches tracked)
- GitHub launches Copilot Verified Proficiency to score real-world coding skills
GitHub introduces Copilot Verified Proficiency, an opt-in Microsoft Pro Badge credential that scores real-world Copilot usage across five engineering skills.
- GitHub previews Copilot app security extension for code alerts
GitHub previews the github-security extension in the Copilot app to inspect, explain or batch-fix code scanning alerts and scan local diffs.
- GitHub previews Copilot Chrome extension and Azure DevOps app support
GitHub opens public previews for its Copilot Chrome and Edge browser extension and Azure DevOps app integration while making GHES support general.
- GitHub and Microsoft Security triage 9,791 AI bug scans in Codename MDASH
GitHub and Microsoft Security preview Codename MDASH, filtering 9,791 raw AI security findings into 99 verified private reports with suggested fixes.

