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

@maafk/mcc

v0.1.3

Published

CLI tool for managing multiple Claude Code workspaces on a single GitHub project

Downloads

32

Readme

mcc

A CLI tool for managing isolated git clone workspaces, designed for running multiple Claude Code agents on the same GitHub project simultaneously.

Each workspace gets its own directory and feature branch, so agents don't step on each other.

Install

Prerequisites: Node.js 18+, git, and optionally gh CLI for PR creation and default branch detection.

npm install -g @maafk/mcc

Or from source:

git clone https://github.com/maafk/mcc.git
cd mcc
pnpm install
pnpm build
pnpm link --global

Quick Start

# Register a repo
mcc init https://github.com/your-org/your-project

# Create a workspace — interactive mode prompts for project and branch
mcc start

# Or specify the branch directly
mcc start feature-auth

# Workspaces are cloned into your current directory:
#   ./your-project/feature-auth/
# Open a terminal there and run claude

# See all workspaces
mcc list

# When done, push and create a PR
mcc finish feature-auth

# Clean up the workspace
mcc clean feature-auth

Commands

| Command | Description | |---------|-------------| | mcc init <repo-url> | Register a GitHub repo (SSH or HTTPS) | | mcc start [branch] | Clone the repo and create a feature branch (interactive if no args) | | mcc list | Show all active workspaces | | mcc status | Show git status and recent commits for each workspace | | mcc finish <branch> | Push the branch, create a PR, optionally clean up | | mcc clean <branch> | Delete a workspace directory and remove from state | | mcc projects | List all registered repos |

Options

start, finish, and clean accept -p, --project <name> to specify which project when you have multiple registered. If omitted with multiple projects, you'll be prompted to select one.

How It Works

  • Workspaces are cloned into your current directory as ./<repo>/<branch>/
  • Global state is tracked in ~/.mcc/state.json
  • Each start does a fresh git clone + git checkout -b
  • finish pushes to origin and uses gh pr create if the gh CLI is available

Development

pnpm install
pnpm test          # run tests
pnpm test:watch    # run tests in watch mode
pnpm build         # compile TypeScript to dist/

License

MIT