Skip to main content

Testing your MCP server with Visual Studio HTTP Files

If you're building or testing Model Context Protocol (MCP) servers and you need a quick way to verify your endpoints are working correctly. Visual Studio's HTTP files (.http) provide an elegant, code-based approach to API testing

What are Visual Studio HTTP files?

HTTP files are plain text files with a .http or .rest extension that let you define and execute HTTP requests directly in your editor. They're supported in Visual Studio, Visual Studio Code (with the REST Client extension), and JetBrains IDEs. Think of them as executable documentation for your API.

Why use HTTP files for MCP testing?

The Model Context Protocol defines a JSON-RPC 2.0 interface for AI model interactions. Testing these endpoints traditionally meant using tools like Postman or curl commands, but HTTP files offer several advantages:

  • Version control friendly: Store your test requests alongside your code
  • Easy sharing: Team members can run the same tests instantly
  • Fast iteration: Make changes and re-run with a single click
  • Environment variables: Switch between dev, staging, and production easily
  • No external tools needed: Everything lives in your IDE

Setting up a basic HTTP file for MCP testing

Create a new file called mcp-tests.http in your project.

Here's a basic structure for testing an MCP server:

Tips for MCP-specific testing

  1. Start with initialization: Always test the initialize endpoint first to ensure your MCP server handshake works correctly.
  2. Test capability negotiation: Verify that your server correctly responds to different client capabilities.
  3. Validate JSON-RPC format: MCP uses JSON-RPC 2.0, so ensure all responses include jsonrpc, id, and either result or error.
  4. Test all tool parameters: For each tool your MCP server exposes, create tests with valid, invalid, and edge-case parameters.

Happy testing!

More information

Use environment specific variables in HTTP files

Use .http files in Visual Studio 2022 | Microsoft Learn

Labels:

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
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

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