top of page

GitHub Copilot team plugin defaults go GA with 8 new MCP connectors

54 minutes ago
7 min read
GitHub Copilot team plugin defaults go GA with 8 new MCP connectors, Data Studios original cover

GitHub has made team customizations for GitHub Copilot generally available, giving team maintainers and organization owners a way to switch on a shared set of approved Agent Plugins for everyone on a team. The feature is limited to Copilot Business and Copilot Enterprise, and the plugins chosen for a team are enabled by default for its direct members in VS Code, the GitHub Copilot app and Copilot CLI. GitHub announced the change in its changelog on November 18, 2026.


On the same day GitHub added eight services to Copilot through GitHub-verified MCP servers, which it calls connectors: Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix. The new connectors are in public preview on all Copilot plans and join more than 25 services that were already available, including Slack, Figma and Sentry. On Business and Enterprise, an administrator has to enable the "Editor preview features" policy before members can use them.


The two releases address the same practical problem from different sides. Team defaults decide which bundles of skills, agents and tool configurations a group of developers starts with, while the connectors widen the set of outside systems Copilot can read from and act on once a developer signs in to them. For companies that already manage Copilot through enterprise policy, neither change overrides existing controls, and the connector rollout may require an update to an MCP allowlist before anyone sees the new services.


··········


GITHUB COPILOT TEAM CUSTOMIZATIONS: HOW TEAM PLUGIN DEFAULTS WORK.


Team customizations sit between two layers that already existed. Individual developers could install plugins for themselves, and enterprise administrators could require or block plugins through managed settings. GitHub describes the new layer as a shared starting point between personal choices and organization-wide policy, set at the level of an organization team on github.com.


The setup runs from the team page. A team maintainer or organization owner opens the organization team, selects the Customize Copilot tab, and then either browses plugins from the built-in marketplaces, the enterprise's own marketplaces or marketplaces the team adds, or adds a marketplace from a GitHub repository that contains a plugin marketplace. Plugins selected there are turned on by default for the team's direct members in VS Code, the Copilot app and Copilot CLI.


Three limits shape how far the defaults reach. Child teams do not inherit the plugins of their parent team, so a nested structure such as an engineering team with platform and mobile sub-teams needs each sub-team configured on its own. Membership must be direct for the defaults to apply. The defaults are also optional for members, who can turn a team plugin off in their Copilot client wherever policy allows it.


GitHub's documentation describes an Agent Plugin as a package that can hold custom agents (*.agent.md files), skills (each with a SKILL.md file), hooks that respond to agent actions, surface-specific extensions such as tools and slash commands, MCP server configurations and, on Copilot CLI, LSP server configurations. Agent Plugins 1.0, which GitHub shipped in August as an open packaging standard developed with AWS, Anysphere, Microsoft, OpenAI and Vercel, puts skills in a skills/ folder and MCP settings in a root mcp.json, with Copilot-specific items kept in a separate directory that other clients ignore. A team default can therefore switch on a whole working setup at once, from a review agent and a set of coding skills to the MCP servers a service team depends on.


··········


WHERE TEAM DEFAULTS FIT IN GITHUB COPILOT PLUGIN POLICY.


Copilot now has several places where plugins can be turned on or locked, and the order between them decides what a developer sees. GitHub's changelog states that enterprise and organization policies take precedence over team defaults, and that Copilot clients keep enforcing allowed marketplaces as well as required and blocked plugins. The documentation adds that managed policy "always wins" and that managed settings can only require or block plugins, which leaves team and repository defaults as the way to turn on optional plugins for a group.


........


Layer

Who sets it

Effect on members

Can a member turn it off

Enterprise managed settings

Enterprise administrators

Requires or blocks plugins and marketplaces

No

Enterprise team managed settings

Enterprise administrators

Adds required plugins through enabledPlugins

No

Organization team defaults (new)

Team maintainers, organization owners

Enables approved plugins for direct members

Yes, where policy permits

Repository defaults

Repository maintainers

Enables plugins via .github/copilot/settings.json

Yes, locally where supported

Personal installs

The developer

Adds plugins for one user

Yes


........


The table explains why GitHub calls team defaults a starting point. A plugin that an enterprise blocks cannot be reintroduced through a team, and a marketplace that policy disallows cannot be used as a source for team or repository defaults. In the other direction, a plugin that an enterprise requires stays on regardless of what a team chooses. Team defaults fill the space in between, where a platform group wants a common toolset for its own developers without forcing the same choice on the whole company.


For administrators the most relevant detail is that turning on team defaults does not need a new policy. Business and Enterprise organizations can start from existing team structures on github.com, and the defaults take effect in the three clients that support Agent Plugins today. GitHub's documentation lists Copilot in the cloud separately, with plugins configured through repository settings, and the changelog does not include it among the clients that receive team defaults.


··········


THE EIGHT NEW GITHUB COPILOT MCP CONNECTORS.


The connector release extends Copilot's list of GitHub-verified MCP servers with services that cover storage, delivery pipelines, scheduling, project tracking, analytics, databases and website building. GitHub's description of each service is short, and the table below follows it.


........


Connector

What Copilot can work with

Box

Content search and management, plus Box AI

Buildkite

Pipelines and builds

Calendly

Scheduling and meetings

ClickUp

Tasks and projects

Mixpanel

Product analytics

Supabase

Projects and databases

Webflow

Sites and content

Wix

Sites and business tools


........


GitHub's own example shows the intended use. A developer asks Copilot why a Buildkite build failed, and Copilot investigates the pipeline and fixes the code in the same session. Once a service is connected, GitHub says it can be used across Copilot, so the same Supabase or ClickUp connection serves the app, the CLI and the editor without separate configuration in each.


The connectors are reached from four places. In the Copilot app a user opens Customize and selects Connect next to the service. In Copilot CLI the /mcp command opens a Connectors tab with the same option. In VS Code the services sit under Customizations in the Agents window, and on github.com they appear on the Copilot customization page. Some services need an administrator on their own side as well; GitHub names Box, where MCP access has to be enabled by a Box admin before the connector works.


··········


WHAT CHANGES FOR COPILOT BUSINESS AND ENTERPRISE ADMINISTRATORS.


The two releases have different plan coverage and different switches, which matters for any organization planning to roll them out together. The summary below is drawn from GitHub's two changelog entries of November 18 and its plugin documentation.


........


Item

Status

Copilot plans

Clients

Admin action needed

Team plugin defaults

Generally available

Business, Enterprise

VS Code, Copilot app, Copilot CLI

Choose plugins on the team's Customize Copilot tab

8 new MCP connectors

Public preview

All plans

Copilot app, CLI, VS Code, github.com

Enable "Editor preview features" on Business and Enterprise

Connectors in a named MCP allowlist

Public preview

Business, Enterprise

All Copilot surfaces

Add each new connector unless the allowlist uses a wildcard


........


The allowlist point is easy to miss. Enterprises that restrict MCP servers by listing each connector individually will not see Box, Supabase or the other new services until an administrator adds them, while enterprises that use a wildcard entry pick them up as soon as the preview policy is on. Because the connectors are a preview, organizations with strict change control may prefer to approve them for a pilot team first, which the new team defaults make simpler to manage when a plugin bundles the matching MCP configuration.


Individual users on Copilot Free, Pro and Pro+ get the connectors without any administrator involvement, since the preview covers all plans. They do not get team defaults, which depend on organization teams and are tied to the Business and Enterprise plans. Readers comparing the two organization tiers will find the differences between the two plans in our GitHub Copilot Business vs GitHub Copilot Enterprise comparison. Teams that already share Copilot workflows through automations can read how those work in our coverage of GitHub Copilot automations and shared team workflows.


GitHub did not announce any price change with either release. Team defaults are part of existing Business and Enterprise seats, and the changelog does not mention separate billing for connector use. GitHub has also not said when the eight connectors will leave public preview.


··········


GITHUB COPILOT TEAM DEFAULTS AND CONNECTORS: CONFIRMED FACTS AND OPEN POINTS.


The confirmed part is specific. Team customizations are generally available on Copilot Business and Enterprise, they enable approved Agent Plugins by default for a team's direct members in VS Code, the Copilot app and Copilot CLI, child teams do not inherit them, members can switch them off where policy allows, and enterprise and organization policies keep priority. The eight new connectors for Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix are in public preview on every Copilot plan, require the "Editor preview features" policy on Business and Enterprise, and may need to be added to named MCP allowlists.


Several points remain open in GitHub's material. The changelog does not say whether team defaults will extend to Copilot in the cloud, which currently takes plugin settings from repositories, or whether nested teams will gain inheritance later. GitHub has given no date for general availability of the connectors and no detail on rate limits or data handling beyond the policies each connected service applies on its own side. For organizations, the practical sequence is to review MCP allowlists and the preview policy first, then use team defaults to give one group a tested plugin bundle before widening it.


··········


FOLLOW US FOR MORE.


·····


DATA STUDIOS


·····


datastudios.org


bottom of page