mcpField
V
vibe3d

vibe3d

Local
github.com/vibebytesOther
Repository

About vibe3d

Edit and render 3D scenes over MCP: rooms, nodes, materials, cameras, and snapshots

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "vibebytes-vibe3d": {
      "command": "npx",
      "args": [
        "-y",
        "@vibebyte/vibe3d-mcp"
      ],
      "env": {
        "VIBE3D_TOKEN": "<VIBE3D_TOKEN>",
        "VIBE3D_HOME": "<VIBE3D_HOME>",
        "VIBE3D_CHROME": "<VIBE3D_CHROME>",
        "VIBE3D_ROOM": "<VIBE3D_ROOM>"
      }
    }
  }
}
Run commandnpx -y @vibebyte/vibe3d-mcp
Environment variables to set
VIBE3D_TOKENSecretDaemon auth token. Prefer this over a command-line flag.
VIBE3D_HOMEDaemon home directory
VIBE3D_CHROMEChrome or Chromium executable. Rendering needs a system browser.
VIBE3D_ROOMRoom id bound when the server starts

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@vibebyte/vibe3d-mcp0.2.8

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.