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

auggie-mcp

v0.1.5

Published

Auggie MCP server wrapper for npx

Readme

Auggie MCP Server

Minimal MCP server exposing Auggie CLI as tools for Q&A and code implementation.

Tools

  • ask_question: Repository Q&A via Auggie’s context engine.
  • implement: Implement a change in the repo; dry-run by default.

Requirements

  • Node.js 18+
  • Python 3.10+ available on the system (used internally; no manual setup needed)
  • Auggie CLI installed (check by running auggie --version) - see installation guide

Authentication (AUGMENT_API_TOKEN)

Retrieve your token via the Auggie CLI:

# Ensure Auggie CLI is installed and on PATH
auggie --version

# Sign in (opens browser flow)
auggie login

# Print your token
auggie --print-augment-token

Provide the token in either of these ways:

  • Cursor/Claude config (recommended): set it under env for the server
{
  "mcpServers": {
    "auggie-mcp": {
      "command": "npx",
      "args": ["-y", "auggie-mcp@latest"],
      "env": { "AUGMENT_API_TOKEN": "YOUR_TOKEN" }
    }
  }
}
  • Shell environment (macOS/Linux)

One-off for a single command:

AUGMENT_API_TOKEN=YOUR_TOKEN npx -y auggie-mcp --setup-only

Persist for future shells (zsh):

echo 'export AUGMENT_API_TOKEN=YOUR_TOKEN' >> ~/.zshrc
source ~/.zshrc

Security tip: never commit tokens to source control. Prefer per-machine environment variables or your client's secure config store.

Configure Clients

Cursor via npx

Use this MCP config in Cursor (global or per-project):

{
  "mcpServers": {
    "auggie-mcp": {
      "command": "npx",
      "args": ["-y", "auggie-mcp@latest"],
      "env": { "AUGMENT_API_TOKEN": "YOUR_TOKEN" }
    }
  }
}

This will:

  • download the wrapper package,
  • create a local Python venv inside the package,
  • install requirements.txt, and
  • launch the Python server in stdio mode.

Quick test via npx (terminal)

# Install deps into the package's local venv (no global installs)
npx -y auggie-mcp --setup-only

# Run the server (stdio). Useful for quick smoke-tests.
npx -y auggie-mcp

# Optional: start HTTP mode for manual debugging
npx -y auggie-mcp -- --http

Claude Desktop (macOS)

Edit ~/Library/Application Support/Claude/claude_desktop_config.json and add:

{
  "mcpServers": {
    "auggie-mcp": {
      "command": "npx",
      "args": ["-y", "auggie-mcp@latest"],
      "env": { "AUGMENT_API_TOKEN": "YOUR_TOKEN" }
    }
  }
}

Security and permissions

  • Default: implement runs in dry‑run mode. No files are written, no shell runs; you get a proposed diff.
  • Enable writes: set dry_run: false.
  • Recommendation: use a feature branch and review the diff before merging.