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

@ai-spec-room/mcp-adapter

v0.1.3

Published

MCP adapter — wires an MCP-capable AI runtime (Claude Code, Cursor, Codex) to the provider-neutral AI Spec Room core API.

Readme

@ai-spec-room/mcp-adapter

MCP adapter that connects any MCP-capable AI runtime (Claude Code, Cursor, Codex) to an AI Spec Room.

Quick start

cd into the folder whose notes you want this session to see, then:

# per room: create .mcp.json from the web UI's curl one-liner
curl -fsSL "https://ai-spec-room.vercel.app/api/rooms/<ROOM_ID>/mcp?token=<TOKEN>" > .mcp.json

# then open your runtime of choice
claude   # or cursor, or codex

The .mcp.json tells the runtime to launch this adapter via npx -y @ai-spec-room/mcp-adapter on demand — no global install required. The adapter treats its current working directory as the private-memory root, so the folder you ran the command in is the folder the AI can search. No path configuration needed.

Private memory scope

The search_my_context MCP tool reads markdown files recursively under the adapter's context root. That root is resolved in this order:

  1. MY_CONTEXT_DIR env var — per-room explicit override
  2. ASR_MY_CONTEXT_DIR env var — shell-level default (e.g. exported in ~/.zshrc)
  3. process.cwd() — fallback, the directory where the runtime launched the adapter

If you want to pin the notes folder regardless of cwd, set ASR_MY_CONTEXT_DIR once:

echo 'export ASR_MY_CONTEXT_DIR=~/notes' >> ~/.zshrc && exec $SHELL

Environment variables

| Var | Required | Purpose | |---|---|---| | CORE_URL | yes | The spec-room core API, usually https://ai-spec-room.vercel.app | | ROOM_ID | yes | Room UUID | | PARTICIPANT_TOKEN | yes | Your A or B token for that room | | MY_CONTEXT_DIR | no | Absolute path to private notes for this room | | ASR_MY_CONTEXT_DIR | no | Shell-level default used when MY_CONTEXT_DIR is not set |