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

ctxpeek

v1.0.0

Published

ctxpeek (pronounced Context Peek) is a local-first MCP server for fresh, version-pinned repo docs.

Readme

ctxpeek

Pronounced Context Peek.

Local-first MCP server for fresh, version-pinned repo docs. ctxpeek lets AI coding assistants read documentation straight from public GitHub, GitLab, or Bitbucket repos at the branch, tag, commit, or monorepo subpath you ask for.

npx -y ctxpeek

Quick Start

Claude Code:

claude mcp add --transport stdio --scope user ctxpeek -- npx -y ctxpeek
claude mcp list

Generic stdio MCP config:

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

Then ask your assistant for docs by repo:

Show me the routing docs from vercel/[email protected]

ctxpeek also resolves fuzzy package names, so the model can turn "drizzle orm" into drizzle-team/drizzle-orm before listing the docs tree.

Why ctxpeek

  • Local stdio MCP process; no ctxpeek account or SaaS query log.
  • Ref-native input: owner/repo@ref#subpath.
  • Works with public GitHub, GitLab, and Bitbucket repos.
  • Reads the requested git snapshot directly, without waiting for docs ingestion.
  • Uses an on-disk cache and CDN/ETag fallbacks to reduce repeat network cost.
  • Returns markdown, not large JSON envelopes.
  • No third-party instruction channel between the upstream repo and your agent.

Context7 vs ctxpeek

The core difference is the AI agent flow.

Context7:
  resolve a library ID
  ask the hosted corpus for docs about a topic
  receive selected context
  answer from that curated bundle

ctxpeek:
  resolve or accept owner/repo@ref
  list the docs tree at that git snapshot
  choose the exact path to inspect
  fetch, peek, compare refs, and repeat as needed

Context7 is strongest when you want curated topic snippets from a hosted corpus. ctxpeek is strongest when the question depends on the exact branch, tag, commit, or monorepo package the docs came from.

Tool Flow

The natural agent loop is:

resolve_repo -> list_docs -> fetch_doc

Additional tools support cheap file previews (peek), diffs between refs (get_changes), changelog slices, related repos, cache status, rate limits, and issue/PR lookup.

Docs

Development

pnpm install
pnpm --filter ctxpeek dev
pnpm --filter ctxpeek test
pnpm --filter ctxpeek test:integration