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

vibe-orchestrator

v0.1.2

Published

AI-powered development orchestration via MCP - cloud brain for multi-agent teams

Downloads

35

Readme

@vibe-orchestrator/server

The VPS-side server for Vibe Orchestrator. Manages kanban state, routes agent tasks, and exposes MCP + REST + SSE + WebSocket endpoints.

Installation

npm install -g vibe-orchestrator

Or run from source:

cd packages/server
bun run dev

CLI Commands

vibe-orchestrator (or bun run src/index.ts)

Start the server. On first run, generates a config file and API key.

| Flag | Env Variable | Default | Description | |------|-------------|---------|-------------| | -p, --port | VIBE_PORT | 4242 | Server listen port | | -d, --data-dir | VIBE_DATA_DIR | ~/.vibe-orchestrator | Data directory |

First Run

=========================================
  Vibe Orchestrator MCP Server
=========================================
  Port:       4242
  Data dir:   /home/user/.vibe-orchestrator
  Health:     http://localhost:4242/health
  MCP:        http://localhost:4242/mcp
  WS:         ws://localhost:4242/ws
  API Key:    a1b2c3d4...
  (Save this key - it will not be shown again)
=========================================

Data Directory Structure

~/.vibe-orchestrator/         (or /var/lib/vibe-orchestrator/ on VPS)
  config.json                 Server configuration + hashed API key
  projects/
    <project-name>.db         SQLite database per project

API Endpoints

Health (Public -- no auth)

| Method | Path | Description | |--------|------|-------------| | GET | /health | Server health, uptime, active sessions, executor status |

MCP (Bearer token auth)

| Method | Path | Description | |--------|------|-------------| | POST | /mcp | MCP Streamable HTTP transport endpoint |

WebSocket (API key in query param)

| Path | Description | |------|-------------| | ws://host:4242/ws?key=API_KEY | Executor WebSocket connection |

REST API (Bearer token or vibe-key cookie)

Authentication

| Method | Path | Description | |--------|------|-------------| | GET | /api/auth?key=API_KEY | Set auth cookie and redirect to /board |

Board & Tickets

| Method | Path | Description | |--------|------|-------------| | GET | /api/board/:project | Get kanban board tree (optional ?status= filter) | | GET | /api/ticket/:id | Get single ticket details | | POST | /api/ticket/:id/move | Move ticket to new status { "status": "..." } |

Sessions

| Method | Path | Description | |--------|------|-------------| | GET | /api/sessions | List sessions (optional ?project= filter) | | GET | /api/sessions/:id | Get session details | | GET | /api/sessions/:id/logs | Get session logs (?offset=0&limit=100) |

Swarms

| Method | Path | Description | |--------|------|-------------| | GET | /api/swarms | List swarms (optional ?project= filter) | | GET | /api/swarm/:id | Get swarm status | | GET | /api/swarm/:id/messages | Get swarm messages (optional ?since=timestamp) |

Other

| Method | Path | Description | |--------|------|-------------| | POST | /api/tickets/generate | AI ticket generation { "prompt": "...", "projectId": "..." } | | GET | /api/executor/status | Check executor connection status |

SSE (Server-Sent Events)

| Path | Description | |------|-------------| | GET /api/events | Real-time event stream |

SSE event types:

| Event | Payload | Description | |-------|---------|-------------| | connected | { ts } | Initial connection confirmation | | heartbeat | { ts } | Keep-alive every 30 seconds | | ticket_created | ticket object | New ticket created | | ticket_moved | ticket object | Ticket status changed | | ticket_updated | ticket object | Ticket fields updated | | swarm_message | swarm message | Message from swarm bus | | session_ended | { sessionId, exitCode, result? } | Agent session completed | | session_error | { sessionId, error } | Agent session errored | | executor_disconnected | { ts } | Executor lost connection |

Authentication

All API and MCP endpoints require authentication via one of:

  1. Bearer token -- Authorization: Bearer YOUR_API_KEY header
  2. HttpOnly cookie -- vibe-key cookie (set via /api/auth?key=...)

The API key is generated on first server start. The server stores only the SHA-256 hash. To rotate the key, delete config.json and restart.

Environment Variables

| Variable | Default | Description | |----------|---------|-------------| | VIBE_PORT | 4242 | Server listen port | | VIBE_DATA_DIR | ~/.vibe-orchestrator | Data directory path | | NODE_ENV | development | Set to production on VPS |

VPS Deployment

Use the included deployment scripts:

# First-time VPS setup (as root):
bash scripts/deploy/setup-vps.sh

# Deploy from local machine:
bash scripts/deploy/deploy.sh your-vps.example.com root

The setup script installs Bun, Nginx, certbot, creates a systemd service, and configures reverse proxy with WebSocket support.

Development

bun run dev          # Start in dev mode
bun run test         # Run unit + integration tests
bun run db:generate  # Generate Drizzle migrations
bun run db:migrate   # Run migrations