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

tabby-mcp-stdio

v1.0.4

Published

Tabby MCP stdio bridge to HTTP tools

Downloads

1,066

Readme

Tabby MCP STDIO Bridge

This is a bridge server that connects a stdio interface to the HTTP endpoints of Tabby MCP.

Installation

npm install
npm run build

Usage

# Start with default settings
npm start

# Specify the same port that the Tabby MCP server is running on
npm start -- --port 3002

# Enable logging to a file
npm start -- --log-enabled --log-file ~/logs/tabby.log

# Set log level (none, error, info, debug)
npm start -- --log-enabled --log-level debug

# Get help
npm start -- --help

Environment Variables

You can also configure the bridge using environment variables:

  • TABBY_MCP_PORT: Port of the main Tabby MCP server (default: 3001)
  • TABBY_LOG_ENABLED: Set to '1' to enable logging
  • TABBY_LOG_FILE: Path to log file
  • TABBY_LOG_LEVEL: Log level (none, error, info, debug)

Development

npm run dev

Logging

The bridge supports logging to a file with different log levels. You can enable or disable logging at runtime using the toggle-logging utility:

# Enable logging
npm run toggle-logging -- --enable --log-file ~/logs/tabby.log

# Disable logging
npm run toggle-logging -- --disable

# Change log level
npm run toggle-logging -- --log-level debug

# Check current logging status
npm run toggle-logging -- --status

After installation, you can also use the global command:

tabby-toggle-logging --enable --log-file ~/logs/tabby.log

The logging configuration is stored in a .tabby-mcp-logging.json file in the current directory and can be reloaded without restarting the server.