📌Overview

Purpose: To provide a powerful VSCode extension that acts as a Model Context Protocol (MCP) client, facilitating integration between MCP tool servers and GitHub Copilot Chat.

Overview: The Copilot MCP Client enables developers to leverage custom tools and context with GitHub Copilot, enhancing their coding experience through seamless connections to MCP servers. This extension supports a variety of server configurations and promotes the development of interoperable AI applications.

Key Features:

MCP Server Management: Effortlessly connect and manage multiple MCP servers with a user-friendly interface.
Copilot Integration: Allows direct access to MCP tools within GitHub Copilot Chat, enhancing productivity.
Tool Discovery: Automatically identifies and displays available tools from connected MCP servers, streamlining usage.
Server Health Monitoring: Provides real-time status updates on MCP servers, ensuring reliable performance.
Automatic Connection Management: Facilitates the smooth handling of server connections and reconnections, minimizing disruptions.
Tool Invocation Support: Fully supports invocation of MCP tools via Copilot Chat, maximizing utility.
Multiple Server Types: Accommodates both process-based and SSE servers for versatile application.
Configuration Migration: Streamlines the upgrade of server configurations to the latest formats automatically.
Server Configuration Command: Offers manual commands for updating legacy configurations.

Copilot MCP Client for VSCode

Please Read!

Since the VSCode team has officially brought MCP support to Copilot, this extension will now defer to their implementation. All existing configurations will be automatically migrated to the official VSCode implementation.

A powerful VSCode extension that acts as a Model Context Protocol (MCP) client, enabling seamless integration between MCP tool servers and GitHub Copilot Chat. Join the growing ecosystem of interoperable AI applications with flexible integration options.

📑 Table of Contents

Features
MCP Feature Support
Installation
Configuration
Usage
FAQ
Requirements
Benefits
Contributing
Author
License

✨ Features

🔧 MCP Server Management: Connect and manage multiple MCP servers through an intuitive UI
🚀 Copilot Integration: Expose MCP tools directly to GitHub Copilot Chat participants
🎯 Tool Discovery: Automatically discover and surface available tools from connected MCP servers
⚡ Server Health Monitoring: Real-time monitoring of MCP server status and connections
🔄 Automatic Connection Management: Seamless handling of MCP server connections and reconnections
🛠️ Tool Invocation Support: Full support for MCP tool invocation through Copilot Chat
🔄 Multiple Server Types: Support for both process-based and SSE (Server-Sent Events) servers
🛡️ Configuration Migration: Automatic migration of server configurations to the latest format
🧩 Server Configuration Command: Manual migration command for updating older configurations

🚀 Usage

Open the MCP Servers view from the VSCode activity bar
Add and configure your MCP servers
Enable/disable servers as needed
Use GitHub Copilot Chat with your connected MCP tools using the @mcp participant
View server status and tool availability in real-time

❓ FAQ

Why aren't my servers appearing in the server list?

This is typically caused by connection timeouts between the MCP SDK and your servers. Here's how to fix it:

Use absolute paths for your executables - instead of relative paths, specify the full path to your executable, for example:
```
/home/<user>/.nvm/versions/node/v<version>/bin/npx figma-developer-mcp --stdio --figma-api-key=...
```
Find your executable paths by running in your terminal:
```
which npx    # or node, uvx, etc.
```

Using absolute paths helps prevent connection issues and ensures the MCP SDK can reliably launch your servers.

Why doesn't tool calling work with Claude 3.7?

The tool calling limitations are imposed by the VSCode API and Copilot Chat. The tool calling models are limited to Claude 3.5 and GPT-4o. If you face issues, try switching between these models. You can force tool calls by using the '#' key and selecting the tool manually in your query.

How can I use the MCP server tools in Copilot Edits?

You can use the tools in Copilot Edits mode by manually specifying the tool(s) with the '#' key and selecting the tool from the list.

Why isn't Copilot calling my tool?

GitHub Copilot has an internal system prompt that may discourage tool calls automatically. If this happens, try using the manual tool selection method described above.

🔗 Requirements

VSCode
GitHub Copilot Chat extension
Compatible MCP servers (see Example Servers at https://modelcontextprotocol.io/servers)

🌟 Benefits

Enable Copilot to use custom context and tools through MCP
Join a growing ecosystem of interoperable AI applications
Support local-first AI workflows
Flexible integration options for your development workflow

👥 Contributing

Contributions, issues, and feature requests are welcome! Feel free to check the issues page: https://github.com/VikashLoomba/copilot-mcp/issues.

✍️ Author

Vikash Loomba

Website: https://automatalabs.io
Github: https://github.com/vikashloomba

📝 License

This project is licensed under the GNU General Public License v3.0.

Part of the MCP Client Ecosystem - Enabling interoperable AI tools for developers ⭐️