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

@magic-comment/mcp

v0.3.1

Published

MagicComment MCP server — read and update user comments from your AI agent. By Magic Team.

Readme

@magic-comment/mcp

MagicComment MCP server — let your AI coding agent read user feedback and close the loop (status / reply) directly from its MCP client. By Magic Team.

Quick start

# run the server (what MCP clients invoke)
npx @magic-comment/mcp@latest

# write the config for a client
npx @magic-comment/mcp@latest init --client codex

Clients: codex, claude, cursor, vscode, gemini, opencode.

Configuration (env)

| Var | Purpose | | --- | --- | | MAGIC_COMMENT_SERVER_URL | Collaboration server URL (default ws://localhost:4100). | | MAGIC_COMMENT_API_KEY | Secret key (sk_) — used for reads and writes. | | MAGIC_COMMENT_PROJECT_ID | Optional default project id. | | MAGIC_COMMENT_REVIEW_ID | Optional review override; otherwise uses the project selection. | | MAGIC_COMMENT_AGENT | Optional model/provider hint for model-agnostic clients, e.g. codex for opencode using Codex. |

The secret key is read from the environment only — never a tool argument.

Tools

| Tool | What it does | | --- | --- | | list_comment_threads | List feedback threads for a project review (filter by page/status). | | get_comment_thread | Full thread with messages + anchored element context. | | list_review_pages | Pages of a review with thread counts. | | set_comment_thread_status | Move a thread to In progress or To review (secret key). | | reply_to_comment_thread | Reply on a thread (secret key). | | get_install_command | The command + config to install this server in a client. | | get_project_config | Resolved config (never returns the secret). |

Transport: stdio by default (stdout is reserved for the MCP protocol; logs go to stderr).

Recommended agent loop

  1. Read the thread (get_comment_thread) to understand the request.
  2. Apply the fix in the codebase.
  3. Reply with a summary (reply_to_comment_thread) — a brief note of what you changed, written in the reviewer's language. Replies are attributed to your agent (Claude Code, Cursor, VS Code, …) with its name and logo.
  4. Move the thread to review (set_comment_thread_status) once the reviewer has that context.

Example client config (Cursor ~/.cursor/mcp.json)

{
  "mcpServers": {
    "magic-comment": {
      "command": "npx",
      "args": ["-y", "@magic-comment/mcp"],
      "env": {
        "MAGIC_COMMENT_SERVER_URL": "wss://comments.example.com",
        "MAGIC_COMMENT_API_KEY": "sk_..."
      }
    }
  }
}

Example client config (opencode ~/.config/opencode/opencode.json)

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "magic-comment": {
      "type": "local",
      "command": ["npx", "-y", "@magic-comment/mcp"],
      "enabled": true,
      "environment": {
        "MAGIC_COMMENT_SERVER_URL": "wss://comments.example.com",
        "MAGIC_COMMENT_API_KEY": "sk_...",
        "MAGIC_COMMENT_AGENT": "codex"
      }
    }
  }
}

MAGIC_COMMENT_AGENT is useful for opencode because the MCP handshake only identifies the client as opencode; it does not reliably tell us which model is selected. Set it to codex, claude, gemini, etc. when you want the reply to use a provider/model logo instead of the generic agent icon.

Generated configs (and get_install_command output) always contain the "sk_..." placeholder — substitute your real secret key from the MAGIC_COMMENT_API_KEY environment variable. Keep any file holding the real key out of version control.