News
Microsoft Extends Copilot AI Tech to Xcode, JetBrains IDEs and Eclipse
Microsoft today said it is rolling out new AI controls and configurability for third-party IDEs, announcing public previews of an MCP Registry and Allowlist Controls for GitHub Copilot in Apple's Xcode as well as in JetBrains IDEs and the open-source Eclipse project.
The updates aim to streamline how developers discover and manage Model Context Protocol (MCP) servers directly inside those IDEs while giving enterprise administrators stronger governance over which servers can run.
While third-party IDEs and editors might be seen as competitors to Microsoft's Visual Studio and Visual Studio Code, the company has a history of rolling out GitHub Copilot tech outside of its own camp, treating Copilot as an IDE-agnostic service while using GitHub and Azure to provide the underlying AI infrastructure and enterprise policy controls.
The MCP Registry is described as a directory of MCP servers that developers can browse, install, or remove from inside the IDE; Allowlist Controls let admins specify which MCP servers are permitted, including a registry-only enforcement mode that blocks non-approved servers at runtime. Microsoft notes these capabilities are in public preview and may change, with current enforcement in Xcode based on server-name matching and more granular validation planned.
Details for Developers and Admins
Xcode: Developers open Copilot in Xcode, sign in, choose Configure MCP server in the Copilot chat panel, then browse servers from the Registry or edit the Registry URL. Admin controls appear in GitHub Enterprise under AI Controls or in organization-level Copilot policies, where admins can enable MCP, set the Registry URL, and pick an enforcement mode (Allow all or Registry only). Microsoft flags that Allowlist Controls are available to Copilot Business and Copilot Enterprise customers and that the functionality is available in a pre-release build
JetBrains and Eclipse: In JetBrains IDEs, developers open Copilot Chat and use the MCP Registry icon to browse, install, or uninstall servers; they can also configure a custom Registry URL. In Eclipse, the MCP Registry icon is in the Copilot Chat panel. Admin setup mirrors the Xcode flow in GitHub Enterprise or org-level Copilot policies, with the same two enforcement modes. Microsoft states these features are in nightly or pre-release builds, require a valid Copilot license, and include documentation on Registry format and setup.
Microsoft frames both rollouts as public previews that may evolve, with explicit pointers to pre-release or nightly builds and a Copilot license requirement. Links to official documentation are provided in each post.
Context: Microsoft's Cross-IDE Expansion
The new MCP Registry and Allowlist Controls follow a series of moves bringing Copilot capabilities to non-Microsoft IDEs. For Apple's Xcode, GitHub first announced Copilot code completion in public preview, and later surfaced Copilot Chat as a public preview offering. Microsoft has also published additional Xcode-focused enhancements over time.
On the JetBrains and Eclipse fronts, Microsoft and GitHub have delivered Copilot Extensions support in JetBrains IDEs, full compatibility updates aligned to JetBrains platform releases, Copilot Edits and @project context for codebase-level chat in JetBrains, and Agent Mode plus MCP support for JetBrains and Eclipse. These precedents reflect Microsoft's strategy mentioned above.
For these previews, Microsoft is seeking feedback at the GitHub Copilot for Xcode Feedback channel, along with GitHub Copilot for JetBrains IDEs and GitHub Copilot for Eclipse.
About the Author
David Ramel is an editor and writer at Converge 360.