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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@johnpapa/peacock-mcp

v1.1.15

Published

Peacock Docs MCP Server demo

Downloads

27

Readme

Open project in GitHub Codespaces smithery badgeNode version License

FeaturesToolsSetupConfiguring an MCP Host

MCP Server for the Peacock extension for VS Code, coloring your world, one Code editor at a time. The main goal of the project is to show how an MCP server can be used to interact with APIs.

Note: All data used by this MCP server is fetched from the official Peacock documentation.

🔧 Features

  • Fetch Peacock docs: Get detailed info on Peacock.

🧰 Tools

1. fetch_peacock_docs 🔍🦸‍♂️

  • Description: Fetches the Peacock for VS Code extension docs from its GitHub repository and answers questions based on the documentation
  • Input:
    • prompt (query): The question about Peacock.
  • Returns: Your answer!

🛠️ Setup

Install Peacock for VS Code HERE.

Installing via Smithery

To install Peacock MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @johnpapa/peacock-mcp --client claude

Run the MCP Server Locally with MCP Inspector

If you'd like to run MCP Inspector locally to test the server, follow these steps:

  1. Clone this repository:

    git clone https://github.com/johnpapa/-peacock-mcp
  2. Install the required dependencies and build the project.

    npm install
    npm run build
  3. (Optional) To try out the server using MCP Inspector run the following command:

    # Start the MCP Inspector
    npx @modelcontextprotocol/inspector node build/index.js

    Visit the MCP Inspector URL shown in the console in your browser. Change Arguments to dist/index.js and select Connect. Select List Tools to see the available tools.

Running the MCP Server hosted in GitHub Copilot with VS Code Insiders

Note: If you already have the MCP server enabled with Claude Desktop, add chat.mcp.discovery.enabled: true in your VS Code settings and it will discover existing MCP server lists.

If you want to associate the MCP server with a specific repo, create a .vscode/mcp.json file with this content:

{
  "inputs": [],
  "servers": {
    "peacock-mcp": {
      "command": "npx",
      // "command": "node",
      "args": [
        "-y",
        "@johnpapa/peacock-mcp"
        // "_git/peacock-mcp/dist/index.js"
      ],
      "env": {}
    }
  }
}

If you want to associate the MCP server with all repos, add the following to your VS Code User Settings JSON:

"mcp": {
  "servers": {
    "peacock-mcp": {
      "command": "npx",
      // "command": "node",
      "args": [
        "-y",
        "@johnpapa/peacock-mcp"
        // "/Users/papa/_git/peacock-mcp/dist/index.js"
        // "_git/peacock-mcp/dist/index.js"
      ],
      "env": {}
    }
  }
}
"chat.mcp.discovery.enabled": true,

Using Tools in GitHub Copilot

  1. Now that the mcp server is discoverable, open GitHub Copilot and select the Agent mode (not Chat or Edits).

  2. Select the "refresh" button in the Copilot chat text field to refresh the server list.

  3. Select the "🛠️" button to see all the possible tools, including the ones from this repo.

  4. Put a question in the chat that would naturally invoke one of the tools, for example:

    How do I set my VS Code accent colors?

    Note: If you see "Sorry, the response was filtered by the Responsible AI Service. Please rephrase your prompt and try again.", try running it again or rephrasing the prompt.