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

@m.huda/mcp-playground

v1.0.6

Published

Short description This repository contains an MCP (Model Context Protocol) server implementation packaged as the npm package `@m.huda/mcp-playground`. The server exposes a small set of tools over the MCP server API and runs over stdio when started.

Readme

mcp-playground

Short description This repository contains an MCP (Model Context Protocol) server implementation packaged as the npm package @m.huda/mcp-playground. The server exposes a small set of tools over the MCP server API and runs over stdio when started.

Key files

  • src/mcp-server.ts — MCP server definition and registered tools.
  • src/index.ts — Entrypoint wiring the server to a stdio transport.
  • build/index.js — Compiled output used by the published package and the local run entry.
  • package.json — Project metadata, scripts, and the package bin declaration.

What this project implements

  • Tools registered by the server (examples):
    • GET_DEVICE_LIST — fetches a device list from a public API.
    • ADD_NEW_DEVICE — accepts a device payload (validated with zod) and posts it to the public API.

These are implemented in src/mcp-server.ts and exposed through the MCP server instance created there.

How to run locally (development)

  1. Install dependencies:
npm install
  1. Run with fast reload (development):
npm run dev
  1. Build and run the compiled output:
npm run build
npm run start
# or
node build/index.js

How to run the published / "cloud" server

This package is published as @m.huda/mcp-playground. The published package exposes a bin which runs the compiled build/index.js. You can run the cloud/published server through npx:

npx @m.huda/mcp-playground

To publish a new release (example flow):

npm run build
npm run publish-minor

MCP servers config (used by tooling)

This JSON snippet is included here so tooling or other projects can easily reference the cloud and local server entries used during development and testing.

{
  "mcpServers": {
    "mcp-playground": {
      "command": "npx",
      "args": [
        "@m.huda/mcp-playground"
      ]
    },
    "mcp-playground-local": {
      "command": "node",
      "args": [
        "D:\\GITHUB\\mcp-playground\\build\\index.js"
      ]
    }
  },
  "preferences": {
    "menuBarEnabled": true
  }
}

Notes

  • The cloud entry (mcp-playground) runs the published npm package via npx and is useful for quickly testing the published server without building locally.
  • The local entry (mcp-playground-local) runs the compiled build/index.js directly from your working tree and is convenient for debugging local changes.