Skip to main content

Hands-on with MCP Resources in Visual Studio

In the first post of this series, we explored what MCP resources are and why they're the overlooked piece of the MCP puzzle. In a second post we showed how to use MCP resources in Visual Studio Code. Before I continue with a next post on building your own MCP server, I first want to show you how Visual Studio handles MCP resources.

Setting up your MCP server with resources in Visual Studio.

Let's start by installing an MCP server that provides resources. We'll use the GitHub MCP Server as our example because it's widely used and demonstrates several resource patterns.

We’ll use an mcp.json file to configure our mcp server:

  • Create .vscode/mcp.json in your workspace root
  • Add your server configuration:
  • Save the file—Visual Studio will detect it and try to load the MCP server.
  • If you now try to use this MCP server, you’ll notice that it doesn’t work yet.
  • This is because we first need to authenticate and fetch an OAUTH token.
  • Click on the … next to the MCP server and click on the Authentication option
  • On the Authentication popup, click on Authenticate.

Using MCP resources

Once you have an MCP server installed and running, let's explore its resources.

  • Click on the + icon in the chat menu and choose MCP resources:

 

  • Choose the MCP resource template you want to use and provide the necessary parameters
    • Remark: Notice that the path used in the Github MCP server is case sensitive!

 

  • Now our agent can use this resource in the same way as a local resource.

That’s it!

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

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more