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

mcp-cmd

v0.1.0

Published

A Node.js CLI for managing persistent MCP servers in the background

Readme

mcp-cmd

A simple Node.js-based command line MCP Client that exposes commands for listing and calling MCP tools.

Why?

There are other command line MCP Clients out there, but all of them spawn the referenced MCP Servers for every tool call.

mcp-cmd is different: you use its CLI to start and stop MCP servers, and the servers run in the background. That means successive tool calls to an MCP Server are handled by the same running instance of that server.

Usage

First, start a server by giving it a name and the command + args, then interact with it, then stop it.

# Start an MCP server
mcp-cmd start <servername> <...url-or-commands>

# List server tools
mcp-cmd tools <servername>

# Call a tool provided by the server
mcp-cmd call <servername> <toolname> --arg1=value1 --arg2=value2

# Stop the MCP server
mcp-cmd stop <servername>

Example

# start server
mcp-cmd start puppeteer npx -y @modelcontextprotocol/server-puppeteer

# list tools
mcp-cmd tools puppeteer

# navigate to a page, log the title, then take a screenshot
mcp-cmd tools puppeteer navigate --url=https://example.com
mcp-cmd tools puppeteer execute --code=document.title
mcp-cmd tools puppeteer screenshot --name=example

# stop the server
mcp-cmd stop puppeteer

Implementation Details

  • dead simple CLI built using sade
  • based on the official @modelcontextprotocol/sdk package
  • only supports starting and stopping MCP servers, listing and calling tools (no resources)
  • stderr from the tool during the call is forwarded to stderr