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

@vibevibes/mcp

v0.10.1

Published

MCP server — connects Claude to vibevibes experiences

Vulnerabilities

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

Links

Git

Maintainers

egemensahinegemensahin

Keywords

vibevibesmcpmodel-context-protocolai-native

Readme

@vibevibes/mcp

Runtime engine + MCP server for vibevibes experiences.

Agents connect via MCP. Humans connect via browser. Same room, same state, same tools.

npm license

Install

npm install @vibevibes/mcp

Quick Start

# Serve an experience (Express + WebSocket + browser viewer)
npx vibevibes-serve ./my-experience

# Or run as an MCP server (for AI agents to connect)
npx vibevibes-mcp

Open http://localhost:4321 in the browser. Connect an agent via MCP. Both are in the same room.

How It Works

  1. You define an experience with @vibevibes/sdk (tools + canvas)
  2. This server loads and runs it
  3. Agents connect via MCP tools (connect, act, look)
  4. Humans open the browser viewer to see the canvas
  5. Everyone shares the same state — tools are the only mutation path
Browser (Canvas)  <--WebSocket-->  vibevibes-serve  <--MCP-->  AI Agent

MCP Tools

| Tool | Purpose | |------|---------| | connect | Join the room. Returns available tools, current state, browser URL | | act | Execute a tool — same tools the human uses via the canvas | | look | Observe current state and recent events | | disconnect | Leave the room |

Features

  • Hot reload — edit src/index.tsx, save, see changes instantly
  • TypeScript bundling — esbuild compiles experiences on the fly
  • Tick engine — optional fixed-rate game loop (netcode: "tick")
  • Protocol mode — load experiences from manifest.json + subprocess
  • Ephemeral state — per-actor transient data (cursors, typing indicators)
  • Agent memory — persistent per-session key-value store

Ecosystem

| Package | Description | |---------|-------------| | @vibevibes/sdk | Define experiences — tools, canvas, state | | @vibevibes/mcp | Runtime engine — MCP server + WebSocket + viewer | | @vibevibes/create | npx @vibevibes/create — scaffold in seconds | | experiences | Example experiences — fork and remix |

License

MIT