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

@atomcut/mcp

v3.6.0

Published

Drive a running AtomCut editor from Claude Code, Claude Desktop, Cursor or any MCP client — every editor verb as a tool, renders as images, the AtomCut skill as resources.

Readme

@atomcut/mcp

Let Claude Code, Claude Desktop, Cursor — any MCP client — drive a running AtomCut editor: design, animate, edit video, generate media, all live on your canvas.

| Your agent app | Add AtomCut | |---|---| | Claude Code | claude mcp add -s user atomcut -- npx -y @atomcut/mcp@latest | | Codex | codex mcp add atomcut -- npx -y @atomcut/mcp@latest | | Gemini CLI | gemini mcp add -s user atomcut npx -y @atomcut/mcp@latest | | VS Code | code --add-mcp '{"name":"atomcut","command":"npx","args":["-y","@atomcut/mcp@latest"]}' | | Cursor · Claude Desktop · anything else | a stdio server: command npx, args ["-y", "@atomcut/mcp@latest"] |

Then in AtomCut: Agents ▸ Use your agent app ▸ Link. That's it — the tab stays linked and reconnects whenever your agent starts a session. Ask for anything: "cut the pauses out of this interview and caption it".

Run as many sessions as you like: they share the one link, each request lands as its own undo step, and closing a session never disconnects the others.

It works with whatever model your agent app runs — MCP is between the app and AtomCut, not the model.

What your agent gets:

  • Every editor verb as a tool — the same ~100 commands AtomCut's own agent uses (create and style layers, keyframes, effects, grading, timeline edits, captions, 3D worlds, character rigs and switches, physics bodies / fields / joints, AI media jobs), with live JSON schemas.
  • Eyes — view_render / view_frames return real renders as images, so it checks its own work.
  • The AtomCut skill as resources (atomcut://skill/SKILL.md and references) — how to work well in the app, plus the default design system.
  • Safety — the bridge listens on 127.0.0.1 only and trusts only AtomCut's own origins (app.atomcut.net, the desktop app, localhost); a tab served from anywhere else must present the pairing token printed on start (also in ~/.atomcut-mcp; extra origins via ATOMCUT_MCP_ORIGINS); every change is labelled with your agent's name in AtomCut's Undo menu, one step per request.

MIT licensed.