verse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERSE_API_KEY | Yes | Verse workspace API key (vk_...) or account token (64 hex) from your Account page/Studio, sent as an Authorization Bearer header. | |
| VERSE_BASE_URL | No | Points at another Verse origin. | https://verse.ctruh.com |
| VERSE_UPLOAD_KEY | No | Optional X-API-Key of a self-hosted server running in keyed mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Verse turns 3D files (GLB, glTF, FBX, OBJ, IFC, USD/USDZ, PLY, SPLAT, SPZ-class captures, point clouds) into a shareable link that opens in any browser, with no app and no plugin. Use upload_scene with a local file path or a public URL, then share the returned link or call get_embed_code for an iframe. Owner actions (list_scenes, visibility, private share links, camera paths) need the user's Verse account token in VERSE_API_KEY. Builds can take a minute or more for large files; if upload_scene returns before the build is done, poll get_scene_status.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| upload_sceneA | Upload a 3D file and turn it into a shareable Verse link that opens in any browser. |
| get_scene_statusA | Check whether an uploaded scene has finished building. Returns |
| list_scenesA | List the scenes owned by your Verse account, newest first: id, link, visibility, size, views and open review comments. Needs VERSE_API_KEY set to your account token. |
| create_share_linkA | Get a link to a scene you own, optionally changing who can open it. |
| revoke_share_linkA | Revoke one private share token so its link stops working. Use the |
| get_embed_codeA | Get copy-paste code to embed a scene in a web page: an |
| list_camera_pathsA | List the guided-tour camera paths of a scene (every scene gets an automatic default path after it builds) and the default one. Returns ids, names, modes (walk/fly), key counts and chapter labels, plus a ready-to-open |
| set_camera_pathA | Create a camera path: a guided walk or fly-through the share link can play. Give 2 to 256 keyframes, each with an eye position |
| reset_auto_camera_pathA | Re-plan the scene's automatic camera path (an eye-height walkthrough for interiors, a drone fly-through for exteriors, a 360 orbit for products) and make it the default. Returns a link that autoplays it. Owner only; needs an account token. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a distinct resource+action target, and the descriptions proactively differentiate the two potentially confusable pairs: set_camera_path vs reset_auto_camera_path ('if you only want a good default tour, use reset_auto_camera_path instead') and upload_scene's returned link vs create_share_link. The remaining mild overlap is that both upload_scene and create_share_link return shareable links, which could momentarily confuse an agent about which to use for sharing an existing scene.
All nine tools follow a clean snake_case verb_noun pattern (upload_scene, get_scene_status, list_scenes, create_share_link, revoke_share_link, get_embed_code, list_camera_paths, set_camera_path, reset_auto_camera_path). Verbs are used consistently per action (list_/get_/create_/set_/reset_) and nouns map to clear resource families (scene, share_link, camera_path).
Nine tools is well within the ideal 3-15 range and each maps to a real step in the 3D hosting workflow: upload, poll status, list, share, revoke, embed, and tour management. No tool appears redundant or filler.
The core workflow (upload → build status → share link → embed → camera tour) is fully covered, but lifecycle gaps exist: there is no delete/remove scene, no update of scene metadata (e.g. rename), and no delete or edit of individual camera paths beyond resetting the auto path. These omissions will force agents to dead-end when cleanup or correction is needed.