copilot-cli-mcp-config

Configure GitHub Copilot CLI MCP servers in mcp-config.json.

5|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/arisng/github-copilot-fc --skill copilot-cli-mcp-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-cli-mcp-config
Source: https://github.com/arisng/github-copilot-fc/tree/main/skills/copilot-cli-mcp-config
Command: npx skills add https://github.com/arisng/github-copilot-fc --skill copilot-cli-mcp-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a streamlined way to configure and manage GitHub Copilot CLI MCP servers via a centralized mcp-config.json, reducing setup complexity and drift between environments.

Core Features & Use Cases

  • Centralized MCP configuration: Store server definitions under the default path ~/.copilot/mcp-config.json or a configurable XDG path.
  • Flexible server types: Define local, stdio, http, or sse MCP servers with straightforward syntax.
  • Migration-friendly: Bridge configurations from VS Code mcp.json to Copilot CLI mcp-config.json and keep environments consistent.

Quick Start

Create and edit the MCP configuration in ~/.copilot/mcp-config.json or your chosen path, then use the Copilot CLI to manage MCP servers with commands like copilot /mcp add, copilot /mcp show, and copilot /mcp remove.

Frequently Asked Questions about copilot-cli-mcp-config

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

FAQPage Schema
How do I configure MCP servers for GitHub Copilot CLI?

Configure GitHub Copilot CLI MCP servers by defining server types like local, stdio, http, and sse in an mcp-config.json file. Store this file under the default ~/.copilot directory or a configurable XDG path to manage your servers centrally.

What is the required structure for a Copilot CLI mcp-config.json file?

The mcp-config.json file requires a root mcpServers key and per-server type and tools definitions. Local and stdio servers require command and args keys, while http and sse servers require a url key, with support for environment variable expansion.

Can I migrate my VS Code MCP server configuration to Copilot CLI?

Yes, you can migrate VS Code mcp.json configurations to Copilot CLI. The process bridges configurations from VS Code to the Copilot CLI mcp-config.json format to keep your local development and team repository environments consistent.

What is the default config path for Copilot CLI MCP servers?

The default config path for Copilot CLI MCP servers is ~/.copilot/mcp-config.json. You can also use a configurable XDG path to store your MCP server definitions for local development and team repositories.

Which MCP server transport types does Copilot CLI support?

Copilot CLI supports local, stdio, http, and sse MCP server types. Each type requires specific keys in the mcp-config.json file, such as command and args for stdio, or url for http and sse connections.

How do I manage Copilot CLI MCP servers after creating the config?

Manage Copilot CLI MCP servers using commands like copilot /mcp add, copilot /mcp show, and copilot /mcp remove. These commands interact with your mcp-config.json to streamline server management and reduce environment drift.