Model Context Protocol

Bring your 3D catalogue into the conversation.

The Vizbl connector lets Claude convert 3D and CAD files, import models into your Vizbl account, follow the conversion pipeline, and produce the AR links, QR codes and product-page buttons that put them in front of shoppers – without leaving the chat. Attach a model file, describe what you want, and Claude does the rest.

Connect the server Browse the tools

Your AI client
You attach a model and ask for an import

OAuth 2.0 · your approval, your scopes

mcp.vizbl.com
Stateless connector – nothing stored here

Optional API key · your account

Vizbl Developer API
Conversion pipeline and your 3D catalogue

Quickstart

Three moves, about a minute.

Add the URL below to your client as a custom connector.
Approve the consent screen. The API key field is optional – leave it empty to start.
Attach a 3D or CAD file and say “convert this to USDZ”. Add a key later to import into your own library.

https://mcp.vizbl.com/mcp

That is it. Everything below is reference – come back when you need it.

Connect in four steps

Vizbl is a remote MCP server: nothing to install, nothing to run locally. Any MCP client that supports remote servers and OAuth can connect.

Add the server to your client

In Claude, add a custom connector with this URL:
```
https://mcp.vizbl.com/mcp
```
In Claude Code, run this in your terminal instead:
```
claude mcp add --transport http vizbl https://mcp.vizbl.com/mcp
```
Transport: Streamable HTTP. Client registration is dynamic – you do not need to pre-register an application with Vizbl.
Authorise the connection

Your client opens the Vizbl consent screen. Review the access being requested and approve. The API key field is optional: leave it empty to connect without a Vizbl account.
Add a secret API key for your own library

Eight of the eleven tools need no Vizbl account. To also import, upload and delete models, create a Developer API key of type secret in your Vizbl account – it starts with sk_live_ and is shown once, at creation time – and paste it on the consent screen. The key is sealed into the encrypted tokens issued to that client and is never stored on our servers. Reconnect at any time to add or change it.
Start working

Attach a 3D or CAD file and ask Claude to convert it, or – with a key – to import it into your library. Access tokens last 60 minutes and refresh silently for up to 90 days; after that you re-approve once.

Tools

Read and write operations are separate tools. Read-only tools run without a prompt each time; the destructive tool always asks for your confirmation first.

Tool	Access	What it does
`get_guide` Get Vizbl guide	Read-only	Returns the official Vizbl guide for a topic: getting started, installation, domains, tokens, try-on types, print dimensions, 3D generation, the converter, scenes and troubleshooting. Claude reads it before explaining how Vizbl works.
`estimate_costs` Estimate token costs	Read-only	Turns traffic and catalogue size into an expected monthly token budget, always as a range with the assumptions named. Tokens only – Vizbl prices are shown on the payment page.
`convert_3d_model` Convert 3D model	Write	Converts and optimises a 3D or CAD file attached to the conversation into GLB, USDZ or FBX. Accepts 14 source formats and returns a conversion job id.
`get_job_status` Get job status	Read-only	Returns the current status of one long-running operation – a conversion or a model import – with its stage, warnings, error and, once finished, its result. Can wait for a bounded time instead of polling.
`create_public_upload_url` Host a file publicly	Write	Hosts a local model or artwork on the Vizbl upload share and returns a public https URL for it. Needed wherever a tool asks for a URL — conversion, or the artwork behind a Wall Art button — and works without a Vizbl account.
`create_upload_url` Create upload URL	Write	Creates a presigned upload session so you can upload a model file from your own device. Returns the upload target and the upload id used by the import tool.
`upload_model` Upload 3D model	Write	Publishes a 3D model in Vizbl from a file attached to the conversation or from an upload id. Supports multi-variant models and optional name, description, tags, category and placement mechanic. Returns an import job id.
`get_ar_link` Get AR link	Read-only	Builds the public link that opens a published object in AR on a phone, from its Object ID.
`get_qr` Get QR code	Read-only	Renders a QR code for an AR link as SVG and PNG, for print, packaging and product cards. Rendered on our servers; the link is never sent to a third-party QR service.
`get_widget_snippet` Get widget snippet	Read-only	Builds the HTML for the product-page AR button: the per-page bootstrap script with its init call, plus the button carrying the object identifiers. Covers the App Clip, native AR and 3D viewer flavours.
`generate_wallart_buttons` Generate wall art buttons	Read-only	Generates a batch of Wall Art try-on buttons from a product list and validates the physical print dimensions, flagging values that look like image resolution.
`delete_model` Delete Vizbl model	Destructive	Deletes an existing Vizbl object by its public Object ID. Claude always asks for confirmation before this runs.

Which tools appear depends on the scopes you granted during authorisation: a connection approved for reading only will not list the import or delete tools. The reference tools – guides, cost estimates, conversion, links and snippets – touch no account data and are always available.

Example prompts

Natural requests – Claude picks the tools. These work as written.

Import this chair.glb into Vizbl, name it “Oak dining chair”, tag it as furniture, and give me the link when it is ready.

Claude calls upload_model with the attached file, then get_job_status until the model is converted, and replies with the public object URL.

What happened to the Vizbl import job I started earlier?

Claude calls get_job_status with the job id and reports the current stage, or the error if the import failed.

Here are three model files for the summer collection – import all of them into Vizbl as wall-mounted objects and summarise the results.

Claude calls upload_model once per file with a shared naming scheme and returns a table of job ids and statuses.

This is a STEP file from our CAD team – turn it into a light GLB we can put on the product page.

Claude calls convert_3d_model, follows it with get_job_status, and offers to import the result into Vizbl.

We have 400 rugs and about 60,000 visitors a month – how many Vizbl tokens should we budget for?

Claude calls estimate_costs and answers with a range, the assumptions behind it and a suggested package – in tokens, never in currency.

Give me the AR button and a QR code for object a1b2c3d4 so I can put them on the product page and the packaging.

Claude calls get_widget_snippet and get_qr, and reminds you to allow-list your storefront domain in Vizbl.

Delete the Vizbl object with tinuuid a1b2c3d4 – we uploaded it twice.

Claude confirms with you first, then calls delete_model for that tinuuid.

What to expect

Practical limits of the hosted connector.

Files and formats

Import formats: glb, gltf, obj, usdz, fbx
Converter accepts: dae, fbx, glb, gltf, iges, igs, obj, ply, step, stp, stl, usd, usdc, usdz
Maximum file size: 200 MB per variant
Source: Files attached to the conversation, or uploaded from your device
Multi-variant: Supported, first variant is the default

Timing and sessions

Wait per call: up to 90 seconds
Access token: 60 minutes
Refresh token: 90 days
Server state: Stateless – no sessions stored

Prerequisites

Nothing is required to start: the reference tools – guides, cost estimates, conversion, links and snippets – need no Vizbl workspace at all. A Vizbl account with Developer API access and a secret API key adds the import, upload and delete tools; imports consume your account's normal conversion quota. The connector does not create accounts, change billing, or generate images, video or audio with AI models.

How your data is handled

The short version – the full text lives in the privacy policy.

Your API key

Encrypted into the OAuth tokens held by your client. The server keeps no copy and no database of connections.

Your model files

Downloaded in memory, forwarded to the Vizbl Developer API under your account, and then discarded. They live in your Vizbl account, as if uploaded through the app.

Your conversation

Only the arguments of a tool call reach the server. We never request chat history, memory, or files unrelated to an import.

Support

Questions, bug reports, and security disclosures.

Get in touch

Email [email protected]. Include the import job id when reporting a failed import – it is the fastest way for us to trace what happened.

Service status of this endpoint: https://mcp.vizbl.com/health

Also from Vizbl

The same Developer API is available directly and through the @vizbl/node SDK, which ships a local MCP server for desktop clients. See vizbl.com.