github-copilot-mcp

Configure and validate Model Context Protocol servers for GitHub Copilot in VS Code.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/schattenspiegel/skill-foundry-skills --skill github-copilot-mcp-schattenspiegel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-copilot-mcp
Source: https://github.com/schattenspiegel/skill-foundry-skills/tree/main/skills/github-copilot-mcp
Command: npx skills add https://github.com/schattenspiegel/skill-foundry-skills --skill github-copilot-mcp-schattenspiegel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Configuring MCP servers for GitHub Copilot in VS Code involves security-sensitive decisions about trust, secrets, transports, and tool scope, and mistakes can leak credentials or grant unintended write authority. This Skill provides a structured workflow for designing, reviewing, and debugging .vscode/mcp.json configurations safely. ## Core Features & Use Cases - Secure Configuration Authoring: Guides creation of .vscode/mcp.json with servers under servers and secret prompts under inputs, keeping tokens out of source control. - Trust and Provenance Review: Verifies server publisher, source, version, executable or URL, license, and authentication method before configuration. - Least-Privilege Scoping: Applies minimal filesystem and network access, sandboxing, and read-only tool preferences. - Use Case: A developer needs to connect Copilot to a remote read-only MCP server. The Skill walks them through verifying the server, writing the JSON configuration without embedded secrets, validating it offline, and performing an approved smoke test. ## Quick Start Ask the assistant to create a secure .vscode/mcp.json configuration for a read-only remote MCP server without embedding any secrets.

Frequently Asked Questions about github-copilot-mcp

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

FAQPage Schema
How do I configure an MCP server for GitHub Copilot in VS Code?▼

Create a .vscode/mcp.json file with server definitions under the servers key and secret prompts under inputs. Verify the server's publisher, version, and authentication method first, then validate the JSON offline before approving startup in VS Code.

How do I keep secrets out of VS Code MCP configuration?▼

Place secret prompts under the inputs section of mcp.json instead of embedding tokens in env, headers, URLs, or arguments. This keeps credentials out of source control while still allowing the server to authenticate at runtime.

What is the difference between stdio and HTTP MCP transports in VS Code?▼

Stdio servers run as local executables and require provenance control and platform-specific sandboxing considerations. HTTP servers connect to remote URLs and require TLS, publisher verification, and authentication that stays out of the repository.

Does this Skill install or start MCP servers automatically?▼

No. Configuration is treated separately from authorization to install, download, start, or authenticate external software. Server startup, trust approval, and smoke testing only happen after explicit separate approval.

When should I not use MCP configuration for a task?▼

Avoid MCP configuration when static repository documentation already supplies the needed context, when implementing an MCP server itself, or when an ordinary HTTP client suffices. Prefer an existing trusted server over generating new command wrappers.