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

instagit

v0.1.8

Published

MCP server for Instagit — AI-powered Git repository analysis for coding agents

Readme

Ask Instagit

Instagit

Let Your Agents Instantly Understand Any GitHub Repo

An MCP server that gives coding agents instant insight into any Git repository — no guessing, no hallucination.

Quick Start

Add to your MCP client configuration:

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}

Install MCP Server

Works with Claude Code, Claude Desktop, Cursor, OpenClaw, and any MCP-compatible client. The @latest tag ensures you always get the most recent version.

Why

Agents that integrate with external libraries are flying blind. They read docs (if they exist), guess at APIs, and hallucinate patterns that don't match the actual code. The result: broken integrations, wrong function signatures, outdated usage patterns, hours of debugging.

When an agent can actually analyze the source code of a library or service it's integrating with, everything changes. It sees the real function signatures, the actual data flow, the patterns the maintainers intended. Integration becomes dramatically easier and less error-prone because the agent is working from ground truth, not guesses.

What Agents Can Do With This

  • Integrate with any library correctly the first time — "How do I set up authentication with this SDK?" gets answered from the actual code, not outdated docs or training data. Your agent sees the real constructors, the real config options, the real error types.
  • Migrate between versions without the guesswork — Point your agent at both the old and new version of a library. It can diff the actual implementations and generate a migration plan that accounts for every breaking change.
  • Debug issues across repository boundaries — When a bug spans your code and a dependency, your agent can read both codebases and trace the issue to its root cause — even into libraries you've never opened.
  • Generate integration code that actually works — Instead of producing plausible-looking code that fails at runtime, your agent writes integration code based on the real API surface: actual method names, actual parameter types, actual return values.
  • Evaluate libraries before committing — "Should we use library A or B?" Your agent can analyze both implementations, compare their approaches to error handling, test coverage, and architectural quality, and give you a grounded recommendation.
  • Onboard to unfamiliar codebases in minutes — Point your agent at any repo and ask how things work. It answers from the code itself, with file paths and line numbers, not from memory that may be months out of date.

Features

  • Agent-native context — Purpose-built for coding agents. Returns the exact context an AI needs to understand, modify, and reason about code.
  • Architectural truth — Goes beyond keyword search. Understands how components connect, why decisions were made, and where the real complexity lives.
  • Any repo, any scale — From weekend projects to massive monorepos. Public and private repositories, any Git host.
  • Exact source citations — Every claim traced back to specific files and line numbers. No hallucination, no hand-waving.

Configuration

Environment Variables

| Variable | Description | Default | |---|---|---| | INSTAGIT_API_KEY | API key from instagit.com | Auto-registers anonymous token | | INSTAGIT_API_URL | Custom API endpoint | Production API |

Authenticated Usage

Sign up at instagit.com for higher rate limits and faster analysis:

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"],
      "env": {
        "INSTAGIT_API_KEY": "ig_your_api_key_here"
      }
    }
  }
}

Anonymous Usage

No API key required — the server automatically registers an anonymous token on first use. Anonymous tokens are stored in ~/.instagit/token.json and shared with the Python MCP server.

Tool: ask_repo

Analyze any Git repository with AI.

Parameters:

| Parameter | Type | Required | Description | |---|---|---|---| | repo | string | yes | Repository URL, shorthand (owner/repo), or any public Git URL | | prompt | string | yes | What to analyze or ask about the codebase | | ref | string | no | Branch, commit SHA, or tag (default: repository's default branch) |

Example prompts:

  • "Explain the architecture and main components"
  • "Review the authentication implementation for security issues"
  • "How would I add a new API endpoint following existing patterns?"
  • "What would it take to upgrade from React 17 to 18?"

Requirements

  • Node.js 18+

License

MIT — Copyright (c) 2026 Instalabs, LLC


Learn more at instagit.com