Edit and render 3D scenes over MCP: rooms, nodes, materials, cameras, and snapshots.
Connect Runs on your machine
claude mcp add vibe3d -e VIBE3D_TOKEN=<VIBE3D_TOKEN> -e VIBE3D_HOME=<VIBE3D_HOME> -e VIBE3D_CHROME=<VIBE3D_CHROME> -e VIBE3D_ROOM=<VIBE3D_ROOM> -- npx -y @vibebyte/[email protected]{
"mcpServers": {
"vibe3d": {
"command": "npx",
"args": [
"-y",
"@vibebyte/[email protected]"
],
"env": {
"VIBE3D_TOKEN": "<VIBE3D_TOKEN>",
"VIBE3D_HOME": "<VIBE3D_HOME>",
"VIBE3D_CHROME": "<VIBE3D_CHROME>",
"VIBE3D_ROOM": "<VIBE3D_ROOM>"
}
}
}
}{
"mcpServers": {
"vibe3d": {
"command": "npx",
"args": [
"-y",
"@vibebyte/[email protected]"
],
"env": {
"VIBE3D_TOKEN": "<VIBE3D_TOKEN>",
"VIBE3D_HOME": "<VIBE3D_HOME>",
"VIBE3D_CHROME": "<VIBE3D_CHROME>",
"VIBE3D_ROOM": "<VIBE3D_ROOM>"
}
}
}
}{
"servers": {
"vibe3d": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vibebyte/[email protected]"
],
"env": {
"VIBE3D_TOKEN": "<VIBE3D_TOKEN>",
"VIBE3D_HOME": "<VIBE3D_HOME>",
"VIBE3D_CHROME": "<VIBE3D_CHROME>",
"VIBE3D_ROOM": "<VIBE3D_ROOM>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
VIBE3D_TOKENOptional, secret | Daemon auth token. Prefer this over a command-line flag. |
VIBE3D_HOMEOptional | Daemon home directory |
VIBE3D_CHROMEOptional | Chrome or Chromium executable. Rendering needs a system browser. |
VIBE3D_ROOMOptional | Room id bound when the server starts |
Details
| Package | @vibebyte/[email protected] (NPM, stdio) |
| First published | 3 Nov 2026 |
| Last updated | 3 Nov 2026 |
| Registry name | io.github.vibebytes/vibe3d |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.