Add the Wopee.io MCP server to Visual Studio
Connect GitHub Copilot in Visual Studio 2026 or Visual Studio 2022 (17.14 or newer) to your Wopee.io project, so the agent can generate tests, run them with Wopee.io's testing agent and read the verdicts. What the server does: Wopee.io MCP server.
Before you start: Node.js 20.18 or newer, and WOPEE_API_KEY and WOPEE_PROJECT_UUID from More › Settings › API Keys in your project (how).
Let your agent do the setup
Set me up for Wopee.io: follow https://wopee.io/agent-setup/prompt.md, show me the plan first, and ask before changing anything.
It shows a plan, runs npx -y @wopee-io/init after your yes, and you approve in Commander, so your API key never reaches the chat. What the agent does. Rather do it by hand? Follow the steps below.
Add the server
In Copilot Chat, switch to Agent mode, open Tools, click + and choose Add custom MCP server. Or create the file yourself:
{
"servers": {
"wopee": {
"type": "stdio",
"command": "npx",
"args": ["-y", "wopee-mcp"],
"env": {
"WOPEE_API_KEY": "your-api-key",
"WOPEE_PROJECT_UUID": "your-project-uuid"
}
}
}
}
Visual Studio MCP config file location
Visual Studio looks for MCP configuration in this order:
%USERPROFILE%\.mcp.json(you, all solutions)<solution folder>\.vs\mcp.json<solution folder>\.mcp.json.vscode\mcp.json.cursor\mcp.json
So a .vscode/mcp.json set up for VS Code is picked up too.
Pass your Wopee.io API key securely
Keep the entry with the key in %USERPROFILE%\.mcp.json, which is outside your repository. Do not commit a solution-level file that contains the key.
Verify the Wopee.io MCP server is connected
Open the tools picker in Copilot Chat (Agent mode). The tools of a new server are disabled by default: enable the wopee tools there.
First prompt to try
How many tests do I have in Wopee.io, and which ones have never run?
Copilot calls wopee_fetch_test_inventory and lists the analyses and test cases in your project with their latest status. More prompts: Prompt library.
Troubleshooting
| Problem | Fix |
|---|---|
| Copilot does not call the Wopee.io tools | Enable them in the tools picker; they are off by default |
| The server is not found | Check the file location and that the top-level key is servers |
[AUTH_ERROR] WOPEE_API_KEY or WOPEE_AUTH_TOKEN must be set |
The env block is missing or empty |
All error messages and their fixes: Troubleshooting.