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

mcpipe

v0.1.0

Published

Decorate stdio MCP servers with debugging and other capabilities.

Readme

mcpipe

npm version total downloads

A wrapper for stdio-based MCP servers that adds debugging, tool name prefixing, and environment management.

Quick Start

# Debug MCP communication
npx mcpipe --debug your-mcp-server

# Avoid tool name conflicts 
npx mcpipe --name myserver your-mcp-server

# Load environment variables
npx mcpipe --env-file .env your-mcp-server

# Combine features
npx mcpipe --debug --name myserver --env-file .env your-mcp-server

Usage in MCP Clients

Prefix your server command with mcpipe:

// Before
{
  "my_server": {
    "command": "npx",
    "args": ["my-mcp-server", "--config", "path/to/config"]
  }
}

// After (with debugging and tool prefixing)
{
  "my_server": {
    "command": "npx", 
    "args": ["mcpipe", "--debug", "--name", "myserver", "npx", "my-mcp-server", "--config", "path/to/config"]
  }
}

Features

Debug Logging (--debug)

  • View all JSON-RPC messages between client and server
  • Monitor process lifecycle events
  • See tool name transformations

Tool Name Prefixing (--name prefix)

  • Run multiple instances of the same server
  • Avoid tool name conflicts between different servers
  • A tool that the server exposes under the name foo will be exposed to your client under the name <prefix>_foo instead

Environment Loading (--env-file path)

  • Load variables from .env files
  • Keep secrets out of MCP client config
  • N.B. if you want only the environment loading without the other features, consider envmcp

Options

  • --debug, -d: Enable debug logging to stderr
  • --name <prefix>, -n <prefix>: Add prefix to tool names
  • --env-file <path>, -e <path>: Load environment file

Debug Output Example

[2024-01-15 10:30:01.125] [myserver_CLIENT→SERVER] {"jsonrpc":"2.0","method":"tools/list","id":1}
[2024-01-15 10:30:01.128] [myserver_SERVER→CLIENT] {"jsonrpc":"2.0","result":{"tools":[{"name":"fetch"}]},"id":1}
[2024-01-15 10:30:01.128] [myserver_TRANSFORM] Tool names prefixed with: myserver_
[2024-01-15 10:30:01.129] [myserver_SERVER→CLIENT] (Modified) {"jsonrpc":"2.0","result":{"tools":[{"name":"myserver_fetch"}]},"id":1}

Environment File Format

KEY=value
ANOTHER_KEY=another value
# This is a comment
QUOTED_VALUE="value with spaces"

License

MIT