Vitrine3d MCP

What vitrine3d/mcp MCP server does

vitrine3d/mcp MCP server connects an MCP-compatible AI client to Vitrine, a 3D product viewer platform with a visual editor. It gives an agent operations for managing GLB model assets, changing how scenes are displayed, publishing models, and producing embed HTML for websites.

Model management includes listing models with their IDs, names, and publish state; uploading a GLB file from disk; inspecting model details and thumbnails; and deleting a model together with its stored data. The account tools also expose the current plan, usage, and limits, and provide login, logout, and feedback actions.

How it works

The server communicates with an AI client through the Model Context Protocol. In its standard mode, the client starts the package as a local stdio process. The server then communicates over HTTPS with Vitrine's API, which uses Supabase for database, storage, and authentication functions.

A separate HTTP mode is available with the --http flag. It serves a Streamable HTTP MCP endpoint at /mcp; the default port is 3000, and the PORT environment variable can change it. This mode is intended for MCP clients or connectors that support HTTP transport.

The server can operate without an API key for anonymous uploads, but those uploads expire after 48 hours. Signing in through the agent opens a browser and makes models permanent. An API key can also be supplied through the VITRINE_API_KEY environment variable.

Setup and configuration

Add the package as a local MCP server in the client configuration:

{
  "mcpServers": {
    "vitrine": {
      "command": "npx",
      "args": ["@vitrine3d/mcp"]
    }
  }
}

For non-interactive execution, use npx -y @vitrine3d/mcp. The package is documented for Claude Code, Cursor, and Windsurf configurations. To retain models beyond the anonymous 48-hour period, ask the agent to log in and complete the browser sign-in flow, or configure an API key generated from the Vitrine account settings.

To run HTTP transport locally, use npx @vitrine3d/mcp --http. Set PORT before the command when a port other than 3000 is needed.

Tools and capabilities

The vitrine3d/mcp MCP server exposes these groups of operations:

• Models: list, upload, inspect, and delete GLB models.
• Scene configuration: read a model's complete scene configuration, apply patches for lighting, camera, background, and effects, list HDRI environment presets, and retrieve the configuration schema.
• Publishing: publish or unpublish models and retrieve ready-to-paste embed HTML.
• Looks: list saved Looks, apply one to a model, or save a configuration under a name.
• Account: inspect plan and usage information, sign in or out, and submit bug reports or feature requests.

The server also provides MCP resources for the scene configuration schema, HDRI presets, and an embed template. These resources can help an agent determine valid configuration fields and available environment options before changing a scene.

Limitations and notes

The material describes GLB upload support; it does not document support for other model formats. Anonymous uploads are temporary and expire after 48 hours, so persistent model management requires browser login or an API key. The documentation does not specify plan limits beyond making account usage and limits available through a tool.

HTTP transport requires an MCP client or connector that supports Streamable HTTP. The local stdio setup is the documented default. The project is released under the MIT license.