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

@builderius/sense-ai

v1.3.2

Published

Builderius Sense — MCP server for AI coding agents

Readme

@builderius/sense-ai

MCP server that connects AI coding agents to the Builderius website builder.

Supported agents

Requirements

  • Node.js >= 22
  • One of the supported CLI agents installed and authenticated

Install

npm install -g @builderius/sense-ai

Usage

Start the Builderius Sense terminal server:

sense

Options

| Flag | Default | Description | |------|---------|-------------| | --agents=LIST | claude | Enabled agents, comma-separated (e.g. claude,gemini,codex). First in list is the default. Each agent gets its own config files and can be launched in separate builder tabs. | | --port=PORT | 7681 | Port to listen on | | --host=HOST | 127.0.0.1 | Bind address |

sense --agents=gemini
sense --agents=claude --port=8080
sense --agents=claude,gemini

Environment variables PORT, HOST, and ENABLED_AGENTS are also supported.

Setup modes

Local (default)

Sense runs on the same machine as WordPress. The Builderius builder starts and manages the server automatically.

  1. Install your CLI agent and log in:
    • Claude Code: curl -fsSL https://claude.ai/install.sh | bash then claude login
    • Gemini CLI: npm install -g @google/gemini-cli then gemini auth login
    • OpenAI Codex: npm install -g @openai/codex then codex auth
  2. Install this package globally (npm install -g @builderius/sense-ai)
  3. On Windows with Claude Code, install Git for Windows (Claude Code requires Git Bash)
  4. In Builderius settings, select your agent, set Sense AI mode to Local
  5. Open the builder — go to the Sense AI tab and click Start Server

Remote

Sense runs on your local machine while the WordPress site is hosted elsewhere (staging server, shared hosting, VM/container).

  1. Install your CLI agent and log in on your local machine (see commands above)
  2. Install this package globally (npm install -g @builderius/sense-ai)
  3. Create a dedicated directory for the remote site and start the server from it:
    mkdir ~/my-remote-site
    cd ~/my-remote-site
    sense
    Sense generates configuration files (instructions, MCP settings, skills) in this directory. Use a separate directory per site to keep each project's context isolated.
  4. In Builderius settings on the remote site, select the same agent, set Sense AI mode to Remote and configure the port
  5. Open the builder — go to the Sense AI tab and enter the connection token
  6. The server accepts the token from the first connection and saves it for future sessions

HTTPS sites: Sense auto-generates a TLS certificate so browsers can connect via wss:// from HTTPS pages. On first connection, the browser may ask you to accept the certificate — click the link shown in the builder, accept the warning, then retry.

Changing the token: If the token changes on the remote site, clear the old token in the builder and enter the new one. The server automatically accepts the updated token.

Docker / DDEV / WSL2

When WordPress runs inside a Docker container (DDEV, Lando, WP Studio, etc.), you must use Remote mode. Local mode cannot work because:

  • PHP inside the container cannot start processes on the host
  • PHP health checks to 127.0.0.1 reach the container's own loopback, not the host where Sense runs

Sense AI, Claude Code, and the MCP server all run on your host machine. Only WordPress is in the container. The browser connects directly to Sense on the host — no special network configuration is needed.

  1. Install your CLI agent and Sense AI on the host machine (not inside the container)
  2. Create a dedicated directory and start Sense:
    mkdir ~/my-docker-site
    cd ~/my-docker-site
    sense
  3. In Builderius settings (on the WordPress site), set the mode to Remote and configure the port
  4. Open the builder — go to the Sense AI tab and enter the connection token

Important: Do not set the mode to "Local" — the builder will show "server is not running" because the PHP health check cannot reach the host from inside the container.

Node.js version compatibility

The package compiles to V8 bytecode for performance. If you upgrade Node.js after installing, the server automatically recompiles on the next start. If auto-recompile fails, reinstall:

npm install -g @builderius/sense-ai

License

Proprietary. See LICENSE for details.