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

ccwiki-mcp

v0.1.6

Published

MCP server for Briefed - real-time codebase context that syncs as your team codes

Readme

@ccwiki/mcp

MCP server that gives Claude Code instant access to your codebase context via ccwiki.ai

What This Does

Once installed, Claude Code automatically has deep understanding of any repository you've analyzed on ccwiki.ai:

  • No more re-explaining your codebase every session
  • No more duplicating code that already exists
  • No more guessing at patterns and conventions
  • Instant context for any task you're working on

Quick Start

1. Analyze Your Repository

Visit ccwiki.ai and analyze your repository. This takes ~10 minutes and creates comprehensive documentation.

2. Get Your API Key

Go to ccwiki.ai/settings and generate an API key.

3. Configure Claude Code

Add to your Claude Code config (~/.claude/config.json):

{
  "mcpServers": {
    "ccwiki": {
      "command": "npx",
      "args": ["@ccwiki/mcp"],
      "env": {
        "CCWIKI_API_KEY": "your-api-key-here"
      }
    }
  }
}

4. Use It

Just start working. Claude Code now automatically has context:

> "Add a new API endpoint for user settings"

Claude knows:
- Where your existing endpoints are
- What patterns they follow
- What middleware to use
- What utilities exist to reuse
- What conventions to follow

Available Tools

Once connected, Claude Code has access to these tools:

| Tool | Description | |------|-------------| | ccwiki_get_context | Get relevant context for a task (patterns, files, conventions) | | ccwiki_find_files | Find files by purpose or layer | | ccwiki_get_conventions | Get coding conventions and anti-patterns | | ccwiki_quickstart | Get a 60-second codebase overview | | ccwiki_search | Search documentation for specific topics | | ccwiki_list_repos | List your analyzed repositories |

How It Works

  1. Auto-detection: The MCP server detects which git repository you're in
  2. Lookup: It finds the matching analyzed repo on ccwiki.ai
  3. Context: It provides relevant context to Claude Code
  4. Caching: Responses are cached for fast repeat access

Environment Variables

| Variable | Description | Default | |----------|-------------|---------| | CCWIKI_API_KEY | Your ccwiki API key | Required | | CCWIKI_API_URL | API base URL | https://api.ccwiki.ai |

Manual Usage

You can also run the server directly:

# Show help
npx @ccwiki/mcp --help

# Show version
npx @ccwiki/mcp --version

# Run server (for testing)
CCWIKI_API_KEY=xxx npx @ccwiki/mcp

Troubleshooting

"Could not find repository"

This means either:

  1. You're not in a git repository
  2. The repository hasn't been analyzed on ccwiki.ai
  3. The git remote URL doesn't match what's on ccwiki

Solution: Make sure the repo is analyzed at ccwiki.ai and you're in the repo directory.

"API request failed: 401"

Your API key is invalid or expired.

Solution: Generate a new API key at ccwiki.ai/settings.

Server not starting

Check that Node.js 18+ is installed:

node --version  # Should be 18.x or higher

Development

# Install dependencies
npm install

# Build
npm run build

# Run in development
npm run dev

# Type check
npm run typecheck

License

MIT

Links