News
Visual Studio Copilot: BYO Model + MCP GA
Microsoft announced two related updates for Visual Studio: support for bringing your own model (BYOM) to Copilot Chat and general availability of the Model Context Protocol (MCP) client in the IDE. The first expands model choice in Chat by letting developers connect API keys from multiple providers. The second formalizes MCP integration to let Copilot connect to authenticated tools and services via standard MCP servers.
These changes target two common requests from enterprise and pro users: choosing specific models for Chat interactions and wiring Copilot to internal systems with governed access. Microsoft published details in Visual Studio Blog posts: Bring Your Own Model to Chat in Visual Studio and Model Context Protocol (MCP) is Now Generally Available in Visual Studio.
Bring Your Own Model to Chat
Visual Studio Chat now accepts API keys from multiple providers for model selection. The post states: "You can connect API keys from providers (OpenAI, Anthropic, and Google) to access a wider range of models." Setup is presented as a short flow inside the Chat model picker, including: "Pick from the preset list, or enter a model name." The announcement also clarifies availability limits: "This feature is not currently available for Copilot Business or Copilot Enterprise users."
[Click on image for larger view.] Model Selection Is Growing (source: video).
Features include:
- Scope: applies only to Chat in Visual Studio (not completions, commit messages, or other AI features).
- Choice and flexibility: switch between Copilot's built-in models and user-configured models via API keys.
- Provider caveats: model capabilities vary; some may not support features such as tool use or vision inputs.
- Pipelines: certain services (e.g., embeddings, repo indexing, intent detection) continue to run through Copilot's API.
- Filtering: output from third-party models is returned directly from the provider and may bypass Copilot responsible AI filters.
To try it, open the Chat window, choose Manage Models in the model picker, select a provider, paste your API key, then select a preset or supply a model name. The model appears in the picker after setup.
MCP Support Is GA in Visual Studio
Visual Studio now includes a full MCP client for connecting Copilot to local or remote MCP servers using .mcp.json configuration.
The MCP is an open standard that lets AI assistants (e.g., GitHub Copilot) connect to external tools, data sources, and services through MCP servers over a consistent, secure interface; in Visual Studio this enables Chat/Agent Mode to reach things like databases, code search, and deployment pipelines without custom one-off integrations.
The announcement summarizes the core: "In Visual Studio, you can connect to local or remote MCP servers using .mcp.json configuration." Authentication is integrated into IDE sign-in flows: "Sign in securely to protected endpoints with built-in Visual Studio flows." To simplify adoption, Visual Studio now supports one-click server installation from the web. For governance, policy administrators can control access: "Your IT admin can now simply navigate to your GitHub policy settings, and toggle on or off MCP features for all users."
Highlights include:
- Full MCP client integration: configure servers, manage inputs and tools, and connect to protected endpoints per the MCP authentication spec.
- Easy add/connect: the tool picker in Copilot Chat includes a green plus button to add servers; the post also notes one-click "Install in VS" from the web.
- Enterprise governance: organization-wide enable/disable controls for MCP via GitHub policy settings.
- Why it matters: custom workflows, enterprise integration to internal tools/APIs, and richer, project-aware conversations in Chat.
Summary
| Area |
Bring Your Own Model (Chat) |
MCP (GA) |
| Primary purpose |
Use provider API keys to select specific LLMs for Chat |
Connect Copilot to tools/services via MCP servers |
| Where it works |
Chat only |
Copilot Chat tool ecosystem (Agent Mode and tools) |
| Key admin controls |
Provider-side usage/quotas/billing |
Org-level enable/disable via GitHub policy |
| Notable caveats |
Not available for Copilot Business/Enterprise; some model features vary; some services still use Copilot API |
Auth handled via IDE; server discovery/install supported; governed by org policy |
About the Author
David Ramel is an editor and writer at Converge 360.