vibe3d runs on your own machine — the client starts it, so there is no endpoint to ping. 2 046 installs a week from npm. Last commit 2 Nov 2026.
Edit and render 3D scenes over MCP: rooms, nodes, materials, cameras, and snapshots.
What the code does
We read the source, 1 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(process.execPath, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add vibe3d -- npx -y @vibebyte/vibe3d-mcp{
"mcpServers": {
"vibe3d": {
"command": "npx",
"args": [
"-y",
"@vibebyte/vibe3d-mcp"
]
}
}
}[mcp_servers.vibe3d]
command = "npx"
args = ["-y", "@vibebyte/vibe3d-mcp"]{
"mcpServers": {
"vibe3d": {
"command": "npx",
"args": [
"-y",
"@vibebyte/vibe3d-mcp"
]
}
}
}{
"servers": {
"vibe3d": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vibebyte/vibe3d-mcp"
]
}
}
}Optional settings from the registry entry, left out of the block above:
VIBE3D_TOKEN (Daemon auth token. Prefer this over a command-line flag), VIBE3D_HOME (Daemon home directory), VIBE3D_CHROME (Chrome or Chromium executable. Rendering needs a system browser), VIBE3D_ROOM (Room id bound when the server starts).
Alternatives to vibe3d
same job, measured the same wayControl KeyShot Studio: scene, cameras, materials from a CMF sheet, and renders
Build editable 3D scenes, direct characters and cameras, and export AI video references with MCP.
MCP server for Reolink cameras: snapshots, device state, AI detection, PTZ, and deterrence controls
Build 3D scenes, place cameras and render shots. Previs, storyboards, set design, product and CAD.
Control local KeyShot scenes, cameras, environments, and renders through headless scripting.
Control Blender from AI: 3D modeling, Geometry Nodes, materials, animation, rendering and export.
Inspect and edit Three.js scenes, materials, shaders, lights in real time from any AI agent
Generate, edit, and render videos via the Shotstack video editing API.
vibe3d — questions
Answers built from our own checks of this server.