npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@mseep/copilot-mcp

v0.0.29

Published

VSCode extension that acts as a Model Context Protocol (MCP) client, enabling integration between MCP servers and GitHub Copilot Chat

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

skydeckaiskydeckai

Keywords

chat-participantcopilotcopilot-mcpchat-participant-utilsdevmcpopenroutercodingagentautonomouschatgptsonnetaillamamseepmcp-server

Readme

Version License: GPL v3 VSCode Extension MCP Client

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 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

  1. Open the MCP Servers view from the VSCode activity bar
  2. Add and configure your MCP servers
  3. Enable/disable servers as needed
  4. Use GitHub Copilot Chat with your connected MCP tools using the @mcp participant
  5. 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:

  1. Use absolute paths for your executables - Instead of relative paths, specify the full path to your executable:

    /home/<user>/.nvm/versions/node/v<version>/bin/npx figma-developer-mcp --stdio --figma-api-key=...

  2. Find your executable paths - Not sure where your executables are located? Run this 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. Unfortunately, the tool calling models are limited to Claude 3.5 and GPT-4o. If you still face issues with tool calls, try switching to one or the other just for the tool you want to run. You can force a tool call in these models 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 its own internal system prompt that may be dissuading tool calls in the chat. If you find that Copilot isn't using your tools automatically, try using the manual tool selection method mentioned above.

🔗 Requirements

  • VSCode
  • GitHub Copilot Chat extension
  • Compatible MCP servers (see Example Servers)

🌟 Benefits

  • Enable Copilot to use custom context and tools through MCP
  • Join the 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.

✍️ Author

Vikash Loomba

📝 License

Copyright © 2024 Vikash Loomba.

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

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