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

codecaine-cli

v0.1.3

Published

Connects the Codecaine web editor to this machine: project folders, live projects, and an MCP server for your coding agent.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

codecainebroscodecainebros

Keywords

Readme

codecaine-cli

Connects the Codecaine web editor to your machine.

npx codecaine-cli            # start it; opens the editor
npx codecaine-cli ./my-app   # and open a project folder

While it runs, the editor in your browser can open and save project folders, keep pictures on disk, and frame your running app on the board through a local proxy, with no changes to the app. Everything stays on your machine. The companion listens on 127.0.0.1 only, and only the editor's own origin can connect to it.

Setting everything up

npx codecaine-cli setup

Starts the companion in the background, downloads and starts its assistant (bb, its own copy, separate from the Codecaine desktop app's), adds the MCP server to Claude Code when it is installed (--no-mcp skips that), and opens the editor. Safe to run again.

Your coding agent

claude mcp add codecaine -- npx -y codecaine-cli mcp

codecaine mcp is an MCP server on stdio. It starts the companion if it isn't running and forwards to it, so every agent shares one companion. Ask your agent to run the project and open it in Codecaine. It starts the dev server and calls openProject, then edits the design with the editor's own tools.

HTTP clients can use http://127.0.0.1:4317/mcp with the bearer token the companion prints.

Options

| | | | --- | --- | | --editor <url> | The editor's address (default https://web.codecainehq.com) | | --origin <a,b> | More origins allowed to connect | | --port <n> | Default 4317 | | --no-open | Don't open the browser | | --no-assistant | Run without the assistant (bb); board requests go to MCP agents |

State lives in ~/.codecaine/web (CODECAINE_HOME to move it).