MCP Server

Use vitrine from AI agents like Claude, Cursor, and Windsurf via the Model Context Protocol.

The vitrine MCP server lets AI agents manage your 3D viewers directly. Upload models, configure scenes, generate embeds — all through natural language.

What you can do

Ask your AI agent things like:

"Upload this shoe model and give me an embed code"
"Make the lighting warmer and add bloom"
"List my models and publish the chair"
"Create a dark Look called 'Noir' and apply it to all my products"
"File a bug: the viewer flickers on Safari"

Setup

Add vitrine to your MCP client config. The config file location depends on your client:

Claude Code: .mcp.json in your project, or ~/.claude/settings.json
Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Cursor: .cursor/mcp.json in your project

With API key (recommended)

Generate a key in the dashboard under Account → API Keys, then add:

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

Without setup (anonymous)

Omit the env block to use anonymous mode. Models expire after 48 hours — sign up to keep them.

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

Available Tools

Models

Tool	Description
`vitrine_list_models`	List all models with IDs, names, and publish status
`vitrine_upload_model`	Upload a GLB file from disk
`vitrine_model_info`	Get model details, thumbnail, and merged config
`vitrine_delete_model`	Delete a model and its storage

Configuration

Tool	Description
`vitrine_get_config`	Get the full scene config for a model
`vitrine_set_config`	Apply a config patch (lighting, camera, background, effects)
`vitrine_list_hdris`	List available HDRI environment presets
`vitrine_config_schema`	Get the full config JSON schema

Showcases & Embeds

Tool	Description
`vitrine_publish`	Publish or unpublish a model
`vitrine_get_embed`	Get ready-to-paste embed HTML

Looks

Tool	Description
`vitrine_list_looks`	List your saved Looks
`vitrine_apply_look`	Apply a Look to a model
`vitrine_create_look`	Save a config as a named Look

Feedback

Tool	Description
`vitrine_feedback`	Submit a bug report or feature request

Account

Tool	Description
`vitrine_account_info`	Current plan, usage, and limits

Resources

The server exposes read-only resources that agents can reference for context:

Resource	Description
`vitrine://config-schema`	Full SceneConfig JSON schema
`vitrine://hdri-presets`	Available HDRI presets
`vitrine://embed-template`	Embed code template

How It Works

You → AI Agent (Claude, Cursor, etc.)
       ↓ MCP protocol
     vitrine MCP Server (runs locally)
       ↓ HTTPS
     api.vitrine3d.com
       ↓
     Supabase (database, storage, auth)

The MCP server runs on your machine and translates tool calls into vitrine API requests. All data stays in your vitrine account.

Compatibility

Works with any MCP-compatible client:

Claude Code / Claude Desktop
Cursor
Windsurf
Cline
Any tool supporting the Model Context Protocol

Environment Variables

Variable	Description
`VITRINE_API_KEY`	Your API key (starts with `vt_`)
`VITRINE_API_URL`	Override the API base URL (for development)

MCP Server

On this page