Vizbl MCP Server: Example workflows

Write to the assistant in plain language. Below are typical requests and what happens behind the scenes.

Publish a 3D model and add it to a product page

Example request: “Upload chair.glb to Vizbl Core AR as ‘Armchair Oslo’, place it on the floor, and give me the AR button for my product page.”

1. If the file is on your computer, the assistant hosts it and gets an https URL.
2. It publishes the model with upload_model and waits for the import job with get_job_status.
3. When the import succeeds, it returns the Object ID and builds the button HTML with get_widget_snippet.
4. You paste the bootstrap script once per site and the button into the product card.

Remember to add your site’s domain to your Vizbl account, otherwise the widget won’t load. See Adding and managing domains.

Convert a CAD file first

Example request: “Convert sofa.step to GLB, keep about half of the triangles, then publish it to Core AR.”

1. The assistant runs convert_3d_model with target_format glb and waits for the conversion job.
2. When it’s done you get a download link for the converted file. Conversion costs no tokens.
3. The converted GLB then goes through the publishing flow above.

Converter tips: a texture size of 2048 px suits most storefronts; use 1024 px for large catalogues on mobile. Files up to 512 MB are accepted.

Share a product in AR offline

Example request: “Make a QR code for object 1a2b3c that opens it in AR, for our print catalogue.”

The assistant builds the AR link with get_ar_link and renders it as a QR code with get_qr.

Create Wall Art buttons for a collection

Example request: “Create Wall Art buttons for these three posters: 50×70 cm, 30×40 cm and 70×100 cm”, followed by the image links.

The assistant runs generate_wallart_buttons. It checks that the print size matches the image aspect ratio and returns the button HTML for each product.

Plan a token budget

Example request: “We have 200 rugs and about 30,000 visitors a month. How many tokens will Vizbl Rugs use?”

The assistant runs estimate_costs and shows the one-time import cost and the monthly usage in tokens. Final prices are shown only on the Vizbl payment page.

Troubleshooting

Example request: “The AR button doesn’t show up on my site. What should I check?”

The assistant reads the official troubleshooting and installation guides with get_guide and walks you through the checks: allowed domain, HTTPS, one bootstrap script per page, and the correct Object ID in the button.

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.