What problem does it solve? Each MCP client (VS Code, GitHub Copilot Web, Visual Studio 17.14+) reads a different config file with a different JSON schema, so wiring up the same RAG and context-mode servers across all three is error-prone and poorly documented. ## Core Features & Use Cases - Side-by-side schema comparison: Documents the config path, root key (servers vs mcpServers), and stdio/HTTP transport support for each of the three clients. - Ready-to-adapt config templates: Provides complete JSON examples for .vscode/mcp.json, .github/copilot/mcp.json, and Visual Studio .mcp/servers.json, including the Docker stdio wrapper and HTTP bearer-token patterns. - Pitfall guidance: Covers common mistakes such as mixing stdio and HTTP for one server, hard-coding localhost in Copilot Web configs, missing mcp-session-id headers, and inline token leaks. - Use Case: You are starting a new project and need Copilot Chat in VS Code, Copilot Web on GitHub, and Visual Studio to all reach your RAG and context-mode MCP servers. This Skill walks you through producing all three config files and smoke-testing each client. ## Quick Start Ask the assistant to set up MCP client configs for VS Code, GitHub Copilot Web, and Visual Studio for your new project using the setup-mcp-clients skill.