copilot

This MCP server enables a Copilot-integrated experience for discovering, installing, and managing open-source MCP servers and agent skills directly from VS Code. It exposes a UI flow to connect to MCP servers, browse available skills (via skills.sh), and install them into your agents, with tight integration to Copilot, Claude, and Codex tools. Use the MCP Servers view to discover remote servers or your local instance, then switch to the Skills tab to search for and install capabilities that extend Copilot’s tooling. The server also supports remote deployments via Cloud MCP, so you can run servers without local setup if you prefer a cloud-based workflow.

Once connected, you can deploy and manage skills per agent, view installed capabilities, and invoke Copilot-powered tooling with the newly added MCP tools. The integration surfaces standardized MCP tool definitions to Copilot/Claude, enabling a more extensible assistant experience across multiple servers and skill sets.

Prerequisites:

• Node.js (recommended: LTS, v14+)
• npm (comes with Node.js)
• VS Code (and optionally the MCP Client extension UI)

Installation steps:

1. Ensure Node.js and npm are installed:

   • On macOS/Linux: curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash - && sudo apt-get install -y nodejs
   • On Windows: download and install from https://nodejs.org/

2. Run the MCP server locally using npx (no global install required):

   • npx -y AutomataLabs.copilot-mcp

3. In VS Code, open the MCP Servers view and add a new server using the command above. You can also use the Cloud MCP option for remote deployment when available.

4. Optionally install the Copilot MCP extension from the VS Code Marketplace to enhance discovery and management capabilities.

5. If you want to contribute or sync upstream providers, clone the repository and run:

   • npm install
   • npm run sync:copilot-provider
   • npm run sync:copilot-provider:check

Tips and known considerations:

• The server can be run locally via npx without a global install; this is convenient for quick testing.
• If you prefer remote hosting, Cloud MCP provides OAuth-based deployment to run MCP servers without local setup.
• When using remote deployment, ensure the Cloud MCP URL is whitelisted in your Copilot/Claude integration settings.
• The MCP client ecosystem is evolving; watch for updates in the vendor/cop encode directory and run npm run sync:copilot-provider to stay in sync with upstream Copilot provider changes.
• If you run into discovery issues, verify network access to the MCP server endpoint and ensure the correct server name is configured in the MCP Servers view.