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

git-repo-explorer-mcp

v0.1.1

Published

MCP server for exploring git repositories with worktree support

Readme

git-repo-explorer-mcp

MCP server for exploring git repositories with worktree support.

Why

  • Fast search - git grep is significantly faster than traditional find/grep for code exploration
  • Multi-branch investigation - Explore multiple branches simultaneously without switching contexts
  • No local clone needed - AI agents can investigate remote repositories without cluttering the local workspace
  • Lightweight - Sufficient functionality for quick code investigation and research tasks

Features

  • Clone repositories as bare repos for efficient storage
  • Worktree support for working with multiple branches simultaneously
  • Read-only operations: ls-files, grep, log, blame, show, diff, branches
  • File content access via cat-file

Installation

npm install git-repo-explorer-mcp

Usage

As MCP Server

Add to your MCP configuration:

{
  "mcpServers": {
    "git-repo-explorer-mcp": {
      "command": "npx",
      "args": ["-y", "git-repo-explorer-mcp", "/tmp/git-repos", "--remind-mcp"]
    }
  }
}

CLI Options

  • --base-dir <path>: Base directory for storing repositories (default: /tmp/mcp-git-<uuid>)
  • --remind-mcp: Add MCP usage reminder to responses
  • --remind-org <text>: Add organization reminder
  • --remind-task <text>: Add task reminder

Actions

Repository Management

| Action | Description | Parameters | |--------|-------------|------------| | clone | Clone a repository | repository (URL), path (optional name) | | repos | List all repositories | - | | remove | Remove repo or worktree | repository, branch (optional) |

File Operations

| Action | Description | Parameters | |--------|-------------|------------| | ls-files | List tracked files | repository, branch, pattern | | cat-file | Show file content | repository, file, branch, ref |

Search

| Action | Description | Parameters | |--------|-------------|------------| | grep | Search in files | repository, pattern, branch, path |

History

| Action | Description | Parameters | |--------|-------------|------------| | log | Commit history | repository, branch, file, limit, format | | blame | Line authorship | repository, file, branch, line | | show | Commit details | repository, ref, branch, file |

Comparison

| Action | Description | Parameters | |--------|-------------|------------| | diff | Show differences | repository, ref, branch, file | | branches | List branches | repository |

Examples

// Clone a repository
{ action: "clone", repository: "https://github.com/user/repo.git" }

// List files on develop branch
{ action: "ls-files", repository: "repo", branch: "develop" }

// Search for TODO comments
{ action: "grep", repository: "repo", pattern: "TODO", branch: "main" }

// Show recent commits
{ action: "log", repository: "repo", limit: 10 }

// Blame a specific file
{ action: "blame", repository: "repo", file: "src/index.ts", line: 42 }

Architecture

Repositories are stored as bare clones in the base directory. When a branch is accessed, a worktree is automatically created under .worktrees/<branch-name>/.

/tmp/git-repos/
├── repo-name/           # Bare repository
│   ├── .worktrees/
│   │   ├── main/        # Worktree for main branch
│   │   └── develop/     # Worktree for develop branch
│   ├── objects/
│   ├── refs/
│   └── ...

License

MIT