Vizbl MCP Server: Overview

Connect Vizbl to Claude and other AI assistants that support the Model Context Protocol (MCP).

The Vizbl MCP server lets an AI assistant work with your Vizbl account directly from a chat. Instead of opening the dashboard, you can ask the assistant to convert a 3D file, publish it to Core AR, and give you an AR link, a QR code or the HTML button for your product page.

What you can do

Convert 3D and CAD files into GLB, USDZ or FBX, with optional optimisation. 14 source formats are supported: dae, fbx, glb, gltf, iges, igs, obj, ply, step, stp, stl, usd, usdc, usdz.
Publish 3D models to Core AR, including models with several variants.
Share products in AR: build an AR link that opens the product on a phone, and render it as a QR code for print, packaging and product cards.
Install the widget: generate the bootstrap script and the AR button HTML for a product card.
Create Wall Art buttons from a product list, with validation of the physical print size.
Estimate token spend for a storefront from catalogue size and traffic.
Read official Vizbl guides on installation, domains, tokens and billing, try-on types, Wall Art dimensions, 3D generation, the converter, scenes and troubleshooting.

A typical first run

Bring in a 3D model. If you already have a GLB, GLTF, USDZ, FBX, OBJ or ZIP file up to 100 MB, ask the assistant to upload it to Core AR. If you only have a CAD file or an unoptimised mesh, ask it to convert the file first.
The assistant waits for the import job to finish. When it succeeds you get an Object ID (called tinuuid in API responses) and a public URL.
Ask for an AR link, a QR code or the widget button for your product page.
Before the button works on a live site, add the site’s domain to your Vizbl account. See Adding and managing domains.

Rugs, Flooring, Wall Art and AI Try-On do not need a 3D file from you. Rugs builds a 3D rug from a flat image and real-world dimensions. Wall Art takes the artwork image and the physical print size directly in the button markup, so there is no catalogue to maintain. Flooring is set up by the Vizbl team.

Tokens

Converting a file costs no tokens. Tokens are spent later, when shoppers load a model in AR, open the widget, upload room photos or run AI try-on attempts. All products share one token balance. See How the token system works in Vizbl.

Security

The public widget key in your page markup is safe to publish. The secret API key used to connect the MCP server is not: never put it in page source.
Deleting a published object is permanent, and buttons and AR links that use its Object ID stop working immediately. The assistant asks you to confirm first.

Current limitations

The MCP server cannot yet list or edit existing models, manage domains, read your token balance, launch 3D generation from photos, or transfer a model to another account. These will be added as the Vizbl Developer API exposes them.

Get help in our Discord

Join our Discord to ask questions about these instructions or get technical support. If something isn’t working, open a ticket and our team will investigate.