Best MCP Servers for VS Code in 2026: 9 Picks for Copilot Agent Mode

The best MCP servers for VS Code in 2026 are GitHub's own server, Microsoft Learn for current docs, Azure and Azure DevOps for Microsoft shops, and Playwright and Chrome DevTools for browser work. MongoDB and Postman round out the list for data and APIs.

In VS Code, MCP servers give GitHub Copilot's agent mode real tools. The VS Code MCP docs let you add servers with MCP: Add Server or by searching @mcp in the Extensions view, where the server gallery is in preview.

We checked every server below against its official docs or repo on 28 October 2026. eSEOspace did not install or test these servers.

How we chose

We included a server only if it passed these tests:

1. Official. Published by the company that owns the product.
2. Works in VS Code. The docs show VS Code setup, an "Install in VS Code" button, or name Copilot agent mode as a client.
3. Clear access model. The docs explain sign-in and scope controls.
4. Clear cost. The docs or pricing page state the price or that it is open source.

We leaned toward Microsoft and GitHub servers, because they fit VS Code teams best. For a broader set of developer servers, see our MCP servers for developers list. If you are still picking an editor, see our MCP clients list.

Where VS Code keeps MCP config

The current docs list ~/.copilot/mcp-config.json for global servers. They label the older workspace .vscode/mcp.json and user-profile mcp.json as deprecated but still supported for compatibility. Many vendor guides still show .vscode/mcp.json, so expect both for a while.

Comparison table

1. GitHub MCP Server: the default for Copilot users

What it is. The GitHub MCP Server is hosted at https://api.githubcopilot.com/mcp/. The README offers one-click VS Code install and says to use "VS Code 1.101 or later for remote MCP and OAuth support."

You pick toolsets to keep the tool list small. With --read-only, write tools are skipped. Our VS Code to GitHub guide walks through it.

Best for: Every team whose code lives on GitHub.

Pricing: Free and MIT-licensed. Copilot itself is priced on the Copilot plans page: Free at $0, Pro at $10, Pro+ at $39 and Max at $100 per month, with MCP listed in agent mode on all of them.

Pros

• OAuth sign-in on the remote server.
• Toolsets and read-only mode.
• Maintained by GitHub.

Cons

• A personal access token overrides OAuth if set, which is easy to forget.
• Broad write access if you load every toolset.

Checked against: GitHub MCP Server README on 28 October 2026.

2. Microsoft Learn MCP Server: trusted docs, no login

What it is. The Microsoft Learn MCP Server at https://learn.microsoft.com/api/mcp lets agents "search through documentation, fetch a complete article, and search through code samples."

"There's no authentication required." The knowledge service does a full refresh once a day.

Best for: Developers working with .NET, Azure, Microsoft 365 or any Microsoft API.

Pricing: "There's no charge to use the MCP server," per the docs.

Pros

• Free with no account.
• Read-only by nature.
• Official, current Microsoft content.

Cons

• Covers public Microsoft docs only.
• Not useful outside the Microsoft stack.

Checked against: Microsoft Learn MCP Server overview on 28 October 2026.

3. Azure MCP Server: Azure resources by chat

What it is. The Azure MCP Server lets agents work with Azure resources and tools like the Azure CLI and azd. It "uses Entra ID through the Azure Identity library."

Tool availability follows your Azure RBAC permissions. Microsoft says the local server "is intended strictly for developer use within your organization." See our VS Code to Azure guide.

Best for: Teams that build and run apps on Azure.

Pricing: The overview lists two prerequisites: "A GitHub Copilot subscription" and an Azure account with the right permissions. No separate MCP charge is listed.

Pros

• Uses your existing Azure sign-in and roles.
• Pairs with Microsoft's Azure Skills plugin.
• Also works in Visual Studio, Cursor and others.

Cons

• Requires a Copilot subscription.
• Broad Azure roles mean broad AI access.

Checked against: Azure MCP Server overview on 28 October 2026.

4. Azure DevOps MCP Server: boards, repos and pipelines

What it is. Microsoft's Azure DevOps MCP has a local server and a remote one at https://mcp.dev.azure.com/{organization}. The README says "We recommend using the Remote MCP Server instead of this local server."

Locally, you load domains such as work items, repositories, wiki and pipelines with -d. You should "Always include core."

Best for: Teams that plan and ship in Azure DevOps rather than GitHub.

Pricing: Free and MIT-licensed. Your Azure DevOps plan still applies.

Pros

• Domains limit which tools load.
• Remote option needs no install.
• Covers work items through pipelines.

Cons

• The remote server is in preview.
• Local setup needs Node.js 20 or later.

Checked against: Azure DevOps MCP on GitHub on 28 October 2026.

5. Playwright MCP: browser automation without screenshots

What it is. Playwright MCP "provides browser automation capabilities using Playwright." It uses "structured accessibility snapshots, bypassing the need for screenshots."

The README gives a one-line install: code --add-mcp '{"name":"playwright","command":"npx","args":["@playwright/mcp@latest"]}'. See our VS Code to Playwright guide.

Best for: Writing end-to-end tests and checking user flows.

Pricing: Free and open source (Apache-2.0).

Pros

• Fast, text-based page snapshots.
• Extra capabilities like PDF and DevTools behind --caps.
• Maintained by Microsoft.

Cons

• The README says "Playwright MCP is not a security boundary."
• The AI sees whatever pages you open.

Checked against: Playwright MCP README on 28 October 2026.

6. Chrome DevTools MCP: performance and debugging

What it is. Chrome DevTools MCP lets an agent "control and inspect a live Chrome browser." It adds performance tracing, network and console debugging.

For VS Code, the README says to run Chat: Install Plugin From Source and enter ChromeDevTools/chrome-devtools-mcp.

Best for: Front-end developers chasing slow pages and console errors.

Pricing: Free and open source (Apache-2.0).

Pros

• Real performance traces.
• Network and console data for debugging.
• Maintained by the Chrome DevTools team.

Cons

• Usage statistics are "enabled by default"; opt out with --no-usage-statistics.
• It "exposes content of the browser instance to the MCP clients."

Checked against: Chrome DevTools MCP README on 28 October 2026.

7. MongoDB MCP Server: data with a read-only default

What it is. The MongoDB MCP Server works with MongoDB databases and Atlas. Its "Install in VS Code" badge runs the server with --readOnly, which "only allows read, connect, and metadata operation types."

You can disable tool categories or operation types with --disabledTools. Our VS Code to MongoDB guide covers setup.

Best for: Developers building on MongoDB or managing Atlas clusters.

Pricing: Free and open source (Apache-2.0). Atlas usage follows your Atlas plan.

Pros

• Read-only by default in the one-click install.
• Fine-grained tool disabling.
• Hosted Atlas plugin with OAuth is also offered.

Cons

• Telemetry is on by default; set --telemetry disabled to turn it off.
• Atlas tools need service account credentials.

Checked against: MongoDB MCP Server on GitHub on 28 October 2026.

8. Postman MCP Server: APIs and client code

What it is. The Postman MCP Server has three remote modes: Minimal at https://mcp.postman.com/minimal, Code, and Full with "all Postman API tools (100+)." The README lists VS Code as supported.

It recommends OAuth on the remote server. "The EU remote server and the local server support only Postman API key authentication."

Best for: Teams that keep API collections and specs in Postman.

Pricing: Free and open source (Apache-2.0). Your Postman plan still applies.

Pros

• Minimal mode keeps context small.
• Code mode generates client code from API definitions.
• EU endpoints available.

Cons

• No OAuth on the EU server.
• Full mode loads 100+ tools.

Checked against: Postman MCP Server README on 28 October 2026.

9. Stripe MCP: payments with a VS Code button

What it is. The Stripe MCP server at https://mcp.stripe.com has an "Install in VS Code" button and a .vscode/mcp.json snippet. It signs in with OAuth or an agent API key.

Stripe "requires human confirmation before it takes certain stripe_api_write actions, such as refunds and outbound payments."

Best for: Developers building checkout and billing code.

Pricing: No separate MCP charge is listed in the docs.

Pros

• OAuth consent per sandbox or live account.
• Human confirmation on risky writes.
• Admins can switch MCP off for the team.

Cons

• From December 2026, Stripe says MCP will reject full-access keys and restricted keys without the Agent tag.
• Live-mode writes need careful approval settings.

Checked against: Stripe MCP docs on 28 October 2026.

Starter sets by team type

You do not need all nine. Too many tools can crowd the agent's context and make tool choice worse, which is why GitHub, Azure DevOps and Postman all let you load fewer tools. Start small and add servers when a real task needs them.

For each server, decide three things before you install it:

1. Scope. Which toolsets, domains or modes will load? Pick the smallest set that does the job.
2. Write access. Can it change data? If so, start in read-only mode or on a test account.
3. Credentials. Does it use OAuth, a token or your local sign-in? Prefer OAuth, and never commit tokens to a shared config file.

Write these choices down in your repo's README or contributing guide. That way new developers get the same reviewed setup instead of copying configs from the internet.

Safety settings worth turning on

The VS Code server management docs advise you to "Review MCP configuration before trusting a repository because stdio servers can run code." Turn on sandboxEnabled for stdio servers on macOS and Linux.

Admins can restrict servers through GitHub's enterprise MCP allowlist, and "Local configuration can't override organizational restrictions." Our Microsoft MCP spotlight covers the wider Microsoft picture.

Next step

Need a private MCP server your VS Code team can use with Copilot? See our MCP development services, or browse more lists in the MCP Guide's best-of section.

Frequently asked questions