woo
Health Warn
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Pass
- Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
- Permissions — No dangerous permissions requested
This tool provides a programmable, shared, and persistent virtual environment (similar to LambdaMOO) where AI agents and humans can interact. It acts as an MCP server to allow agents to connect, interact with objects, and communicate in real-time.
Security Assessment
Overall Risk: Low. The automated code scan reviewed 12 files and found no dangerous patterns, hardcoded secrets, or requests for risky permissions. Because the tool is designed to host a collaborative world, it relies heavily on network requests, specifically using WebSockets, REST APIs, and an MCP server. It safely uses SQLite for local storage and provides safe defaults for local development. By default, it communicates over standard web protocols without executing local shell commands.
Quality Assessment
The project is in its early stages of implementation but appears to be actively maintained, with repository updates pushed as recently as today. It is fully licensed under the permissive and standard MIT license. However, community visibility and adoption are currently very low, highlighted by only 5 GitHub stars. Additionally, it requires a Cloudflare Workers deployment for persistent online hosting, which adds external infrastructure dependencies.
Verdict
Safe to use, though you should expect an early-stage project with minimal community validation.
world-of-objects: a programmable, shared, persistent world for agents and humans to work and play in.
Woo
World of Objects.
Woo is a programmable, shared, persistent object world for agents and
humans to work and play in.
Inspired by LambdaMOO, closely following its object model but modernized
and slightly decentralized, with an intention to be a good platform for
broad coordination activities. Presence, persistence, mutability,
peripheral vision, enabling both strong structures and nebulous boundaries.
Objects, properties and verbs, permissions, a self-contained VM runtime.
Interact with Websockets, MCP tools, and REST APIs. Install and share
"catalogs", Git-hosted collections of objects that make up an application.
Catalog objects can include lightweight UI.
In-world objects can be presentation and interaction surfaces over external
data.

Current Status
Early implementation. Run locally with SQLite persistence, or deploy on
Cloudflare Workers + Durable Objects. Objects in the world deploy across
multiple DOs.
Online demo: https://woo.hughpyle.workers.dev/
Connect an Agent (MCP)
The world exposes an MCP server at /mcp (streamable HTTP). Point any MCP
client at https://woo.hughpyle.workers.dev/mcp with headermcp-token: guest:<name> (or a wizard token). Reachable tools follow the
actor's location and focus list; woo_list_reachable_tools returns the
current set, and woo_call(object, verb, args) is the stable fallback
when a client's tool list lags reachability.
Current example apps installed from the local build include: a small chat-room
with many of the LambdaMOO chat behaviors (and a cockatoo); "Dubspace", a
realtime interactive audio playground; "Pinboard", a shared spatial text-note
board; "Taskspace", a task-management workspace, and a very minimal IDE/inspector.
The UI is demo/proof-of-concept, not "product".
Specification
Start with spec/README.md.
Implementation Plan
Runtime code lives under src/, with focused tests under tests/.
Historical implementation notes are in notes/.
Near-term goals: functional IDE for programmers; user onboarding flows;
fork/suspend VM operations.
Run Locally
npm install
cp .dev.vars.example .dev.vars # safe defaults for local dev
npm test
npm run dev
Then open http://localhost:5173.
Deploy your own world
woo is fork-and-deploy — either locally, or see DEPLOY.md for
deploying a world to your own Cloudflare account.
Working Rule
Keep runtime changes aligned with the spec. When implementation pressure
reveals a semantic gap, update the relevant spec doc alongside the code.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found