Skip to main content

View your installed MCP servers in VSCode

Managing Model Context Protocol (MCP) servers in VS Code has become significantly easier with the dedicated management interface in the Extensions view. While you can configure MCP servers in multiple places throughout VS Code, the Extension tab provides a centralized, visual approach to monitoring and controlling all your available MCP servers.

The challenge of multiple configuration points

VS Code offers several ways to configure MCP servers, which provides flexibility but can also create complexity:

  • Workspace settings via .vscode/mcp.json files for project-specific configurations
  • User settings for global MCP server configurations across all workspaces
  • Automatic discovery of servers defined in other tools like Claude Desktop
  • Direct installation from the curated MCP server list
  • Command-line configuration using the --add-mcp option
  • And more…

While this flexibility is powerful for developers working across different projects and environments, it can make it challenging to get a complete picture of which MCP servers are actually available and running.

The Extensions tab

VS Code addresses this complexity with the MCP SERVERS - INSTALLED section in the Extensions view (Ctrl+Shift+X or ⇧⌘X on Mac). This dedicated interface serves as a command center for all your MCP servers, regardless of where they were configured.


The Extensions tab provides a unified view that shows:

  • All currently installed MCP servers from any configuration source
  • Server status (running, stopped, or error states)
  • Quick access to server-specific actions and information
  • Visual indicators for server health and connectivity

You can manage the MCP server directly from the Extensions tab by right-clicking on any MCP server:

The opened context menu gives you directly access to the following options:

  • Start/Stop/Restart - Control server lifecycle without editing configuration files
  • Show Output - View server logs for debugging and monitoring
  • Disconnect Account - Manage authentication for servers requiring credentials
  • Show Configuration - View the current server configuration
  • Browse Resources - Explore resources provided by the server
  • Configure Model Access - Control sampling permissions for different models
  • Show Sampling Requests - Monitor model access requests
  • Uninstall - Remove servers cleanly from your environment

I really like this addition as it greatly helps working with an growing number of available MCP servers.

Nice!

More information

Use MCP servers in VS Code

MCP Power-User Mode: Revealing Every MCP Feature in VS Code

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more