Shared human-AI experiences. Define tools and a canvas. Agents connect via MCP. Humans connect via browser. Same room, same state, same tools.

npx @vibevibes/create my-experience
cd my-experience
npm install
npx vibevibes-serve .

Open http://localhost:4321. You're the human player. Connect an AI agent via MCP. Build together.

Repo	What it does	npm
sdk	Define experiences — tools, canvas, state
mcp	Runtime engine — MCP server + WebSocket + viewer
create	Scaffold a new experience in seconds
experiences	Example experiences — fork and remix	—

Browser (Canvas)  <--WebSocket-->  vibevibes-serve  <--MCP-->  AI Agent

1. SDK — author an experience: define tools (Zod-validated state mutations) and a React canvas
2. MCP — run it: the runtime serves the experience, agents connect via MCP, humans via browser
3. Same tools — both humans and agents call the same tools. No separate APIs. No backdoors.

• Tools are the only mutation path. No direct state writes. Every action is validated, logged, and broadcast.
• Agents are actors, not assistants. They join rooms, watch for events, and use tools — same as humans.
• One file is an experience. src/index.tsx exports a manifest, tools, and a canvas. That's it.