setup-mcp-clients

Configure MCP client JSON files for VS Code, GitHub Copilot Web, and Visual Studio.

Updated Nov 19, 2020
One-click install
npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill setup-mcp-clients-kwojtasinski-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-mcp-clients
Source: https://github.com/kwojtasinski-repo/ECommerceApp/tree/main/.github/skills/setup-mcp-clients
Command: npx skills add https://github.com/kwojtasinski-repo/ECommerceApp --skill setup-mcp-clients-kwojtasinski-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about setup-mcp-clients

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure MCP servers in VS Code?

Create a `.vscode/mcp.json` file with a `servers` root key listing each server with its type (`http` or `stdio`), URL or command, and arguments. Reload via Command Palette → "MCP: Reload servers" to activate the configuration.

How do I set up MCP servers for GitHub Copilot Web?

Add a `.github/copilot/mcp.json` file to the repository using HTTP transport with publicly reachable HTTPS URLs. Store tokens as GitHub repo secrets referenced via `${env:NAME}`; never inline them, and never use localhost since Copilot Web runs remotely.

What is the difference between VS Code and Visual Studio MCP config files?

VS Code uses `.vscode/mcp.json` with a `servers` root key, while Visual Studio 17.14+ reads `%USERPROFILE%\.mcp\servers.json` or a solution-level `.mcp/servers.json` with an `mcpServers` root key. Visual Studio also requires `docker.exe` instead of bare `docker` for stdio commands.

Can I use stdio and HTTP transport for the same MCP server?

No, mixing transports for the same server across clients causes cryptic serialization errors because a stdio server reads from stdin and cannot serve multiple clients. Pick one transport per server, usually HTTP for multi-client safety.

Why does my MCP HTTP client lose session context between requests?

Modern MCP servers require an `mcp-session-id` header; without it every request starts a fresh session. VS Code and Copilot handle this automatically, but custom Postman or curl scripts must capture the session ID from the first response and reuse it.

When should I not use this MCP client setup skill?

Do not use it to bring up the MCP servers themselves or to diagnose runtime tool errors. Server provisioning belongs to the RAG and context-mode setup skills, and diagnosis belongs to the RAG or context-mode troubleshooting playbooks.