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

claude-cowork

v0.1.0

Published

Lightweight MCP server for coordinating multiple Claude Code terminals

Readme

claude-cowork

Lightweight MCP server for coordinating multiple Claude Code terminals working on the same project.

What it does

When you open multiple Claude Code terminals on the same project, they have no way to know about each other. claude-cowork adds a shared board where each terminal registers what it's working on and which files it's touching. If two terminals try to claim the same file, Claude gets a warning and asks you what to do.

Install

Add to your project's .mcp.json:

{
  "mcpServers": {
    "cowork": {
      "command": "npx",
      "args": ["-y", "claude-cowork"]
    }
  }
}

Then open Claude Code. The server starts automatically.

How it works

  1. Open Claude Code in multiple terminals on the same project
  2. Each terminal auto-joins the board on first interaction
  3. Before starting work, Claude claims a task and lists files it will edit
  4. If files overlap with another terminal, Claude warns you
  5. When done, Claude marks the task complete

Tools

| Tool | Description | |------|-------------| | cowork_join | Register on the board, get an auto-generated name | | cowork_claim | Claim a task and declare files you'll edit | | cowork_board | View all active terminals and their work | | cowork_update | Update your file list mid-task | | cowork_done | Mark task complete, release file claims | | cowork_leave | Remove yourself from the board |

Design

  • Stdio transport — no server to manage, Claude Code spawns it automatically
  • Shared JSON file (~/.cowork/board.json) with proper file locking
  • Warnings, not blocks — file conflicts are surfaced, human decides
  • Auto-purge — terminals with no heartbeat for 5 minutes are removed
  • Auto-generated names — each terminal gets an adjective-animal name (e.g., swift-falcon)