Skip to main content
ClaudeWave

Drop a full augmented-reality studio into any web page. Place any number of 3D models in your real room through the camera, generate new ones from a text prompt, arrange them, then share the scene as a link, a QR code, or a live room. WebXR + Quick Look + Scene Viewer, a free CC0 model library, and an MCP server for agents.

MCP ServersOfficial Registry2 stars0 forksJavaScriptApache-2.0Updated today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (Apache-2.0)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 8/20/2026
Install in Claude Code / Claude Desktop
Method: NPX · 3d-ar-studio
Claude Code CLI
claude mcp add 3d-ar-studio -- npx -y 3d-ar-studio
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "3d-ar-studio": {
      "command": "npx",
      "args": ["-y", "3d-ar-studio"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Use cases

MCP Servers overview

# 3D AR Studio

**Drop a full augmented-reality studio into any web page.**

Place as many 3D models as you like in your real room through the camera, describe a new one
and watch it appear, arrange everything by hand, then share the whole scene as a link, a QR
code, or a live room someone else can build in with you.

[**Live demo**](https://nirholas.github.io/3D-AR-Studio/) · [npm](https://www.npmjs.com/package/3d-ar-studio) · [MCP server](#mcp-server)

```html
<script type="module" src="https://unpkg.com/3d-ar-studio/dist/ar-studio.min.js"></script>
<ar-studio></ar-studio>
```

That is a working AR studio. No build step, no API key, no account. It comes wired to a free
library of a few hundred public-domain models and a free, keyless text-to-3D lane; point it at
your own catalogue with one option when you are ready.

---

## Why this exists

Every web-AR drop-in places exactly one model and then hands off to a native viewer, which
ends the session. This one keeps the whole scene in your page:

- **Many models, one room.** Place, drag, pinch-resize, twist-rotate and duplicate as many
  models as you want in a single live camera view.
- **Generate without leaving the camera.** Type "a brass desk lamp" into the dock. The
  generation runs behind the live view and the finished model drops into the room.
- **Real WebXR where it exists.** An always-armed hit-test reticle, one `XRAnchor` per placed
  model, real-world light estimation, and depth occlusion so models hide behind your furniture.
- **Real ARKit and ARCore everywhere else.** iPhones have no WebXR, so an iPhone gets Apple's
  AR Quick Look instead: true plane detection, true scale, true occlusion. The GLB is converted
  to USDZ on the device (a real conversion via three.js's `USDZExporter`, about a second for a
  typical prop, no server involved). Android without WebXR gets Scene Viewer. Desktop gets a
  grid preview and a QR hand-off to a phone.
- **Scenes are links.** Models, positions, rotations and scales round-trip through the URL.
  Compose on a laptop, scan the QR, it reopens exactly on your phone.
- **Build together, live.** Open a room, share a six-character code, and every add and move
  syncs to everyone in it.
- **Characters actually move.** Any humanoid GLB with no baked animation gets an idle clip
  retargeted onto its own skeleton. No rig allow-list, no T-poses.
- **Agents can drive it.** A bundled MCP server lets Claude, ChatGPT or your own agent
  generate a model, compose an arrangement, and hand a person one link that opens it in
  their room.

The rendering ladder, anchor lifecycle, retargeting pipeline, scene format and shared-room
protocol are extracted from the AR surfaces running in production on
[three.ws](https://three.ws), and generalized so they work on your site with your models.

---

## Install

```bash
npm i 3d-ar-studio three
```

`three` is a peer dependency, so you keep one copy of it and pick the version. The CDN bundle
(`dist/ar-studio.min.js`) has three.js inside it and needs nothing else.

```js
import { createArStudio } from '3d-ar-studio'

const studio = createArStudio('#stage', {
  branding: { title: 'Acme AR', accent: '#00b894' },
})

studio.on('add', ({ placement }) => console.log('placed', placement.title))
```

The studio fills its host element absolutely, so give the host a height (any positioned box
with a real height works; a `<div>` with no height gets a sensible `70vh` default rather than
rendering invisibly).

### Scaffold a deployable page

```bash
npx 3d-ar-studio create my-ar-site     # a folder you can publish as-is
cd my-ar-site
npx 3d-ar-studio dev                   # look at it locally
npx 3d-ar-studio deploy                # push it and turn on GitHub Pages
```

`deploy` prints every `git` and `gh` command before it runs it. It needs
[git](https://git-scm.com) and the [GitHub CLI](https://cli.github.com); without them it tells
you the three manual steps instead of failing silently.

Templates: `static` (one HTML file, no build), `vite`, `react`.

Both `3d-ar-studio` and `ar-studio` run the CLI. The MCP server is a separate
binary in its own package, so `npx 3d-ar-studio-mcp` resolves cleanly: see
[MCP server](#mcp-server).

---

## Your own models

The tray is filled from three.ws by default: a few hundred public-domain (CC0) props, free for
commercial use, served with open CORS. Swap in your own with the `assets` option.

**A JSON file anywhere.** Five common shapes are read without reshaping:

```js
createArStudio(el, { assets: 'https://cdn.acme.com/models.json' })
```

```jsonc
// Any of these work:
[ { "url": "https://cdn.acme.com/chair.glb", "name": "Aero chair" } ]
{ "items":     [ … ] }
{ "objects":   [ … ] }   // three.ws object library
{ "creations": [ … ] }   // three.ws forge gallery
{ "models":    [ … ] }
```

Per entry, the model URL is read from the first present of `src`, `url`, `glb`, `glb_url`,
`glbUrl`, `file` or `model`; the label from `title`, `label`, `name` or `prompt`; and the
thumbnail from `poster`, `thumb`, `thumbnail`, `image` or `preview_image_url`. Anything that
is not an https (or site-relative) URL is dropped rather than handed to the loader.

**A list you hold in code:**

```js
import { staticSource } from '3d-ar-studio/sources'

createArStudio(el, {
  assets: staticSource({
    label: 'Our furniture',
    items: [{ src: 'https://cdn.acme.com/chair.glb', title: 'Aero chair', poster: '…' }],
  }),
})
```

**Several tabs at once, in the order you want them:**

```js
createArStudio(el, { assets: ['recent', myCatalogue, 'objects', 'link'] })
```

Built-in keys: `'three.ws'` (the default set), `'recent'`, `'objects'`, `'community'`, `'link'`.

**Anything else.** A source is an object with a `list()`:

```js
createArStudio(el, {
  assets: {
    id: 'search',
    label: 'Search',
    searchable: true,
    async list() {
      const rows = await fetch('/api/models').then((r) => r.json())
      return rows.map((m) => ({ src: m.glb, title: m.name, poster: m.thumb }))
    },
  },
})
```

Throwing from `list()` is fine: the tray renders a designed error state with a Retry button.

**Your users can retarget it too**, without touching your code: `?assets=https://…/manifest.json`
on the page URL. Only https URLs are accepted, and every model source is re-validated before it
reaches the loader, so a hostile link can add a catalogue but can never smuggle a
`javascript:` or `data:` model into the scene. Set `allowUrlOverride: false` to switch that off.

### CORS

Models are loaded by the browser, so the host serving your `.glb` files has to allow
cross-origin requests (`access-control-allow-origin`). If a model fails to load, that is
almost always why, and the studio says so in the status line rather than failing silently.

---

## Options

| Option | Default | What it does |
| --- | --- | --- |
| `assets` | `'three.ws'` | Where models come from: a preset key, a manifest URL, a source object, or an array of them. |
| `generate` | enabled | `{ enabled, endpoint, kind, tier, timeoutMs, pollMs }`. `endpoint` is any MCP server exposing a compatible generate tool. |
| `rooms` | enabled | `{ enabled, server }`. Point `server` at your own Colyseus deployment to host shared rooms yourself. |
| `animations` | three.ws idle clip | `{ enabled, manifestUrl, clip }`. The clip retargeted onto humanoid models that ship no animation. |
| `lighting` | `'studio'` HDRI | `{ preset, urls }`. `preset: null` uses procedural lighting only and downloads no HDRI. |
| `branding` |: | `{ title, accent, backHref, backLabel }`. |
| `shareBaseUrl` | this page | Where share links and QR codes point. |
| `origin` | `https://three.ws` | Origin for the hosted "View in your space" launcher and viewer links. |
| `persistKey` | `'ar-studio:scene:v1'` | localStorage key for the saved scene. Change it to run two studios on one origin. |
| `persist` | `true` | Restore the last scene on load. |
| `maxPlacements` | `20` | Cap on simultaneous models. Keeps low-end phones interactive. |
| `fullscreen` | auto | Render as a fixed full-screen layer. Defaults to true only when mounted on `document.body`. |
| `allowUrlOverride` | `true` | Honour `?assets=`, `?src=`, `?room=` and `?forge=` on the hosting page's URL. |
| `onEvent` | `null` | Called with `(event, detail)` for every notable action. Wire it to your analytics. |

### URL parameters

| Parameter | Effect |
| --- | --- |
| `?assets=<https url>` | Swap the catalogue. |
| `?src=<glb>&title=<name>` | Load models into the scene. Repeatable. |
| `#s=<payload>` | Reopen a full arrangement, transforms included. Written by `shareUrl()`. |
| `?room=<code>` | Join a shared room. |
| `?forge=<prompt>` | Start a generation on load. |

### Methods

```js
await studio.addModel({ src, title })        // place a model
studio.clear()                               // remove everything; returns what was there
studio.getScene()                            // [{ src, title, x, z, yaw, scale }]
await studio.setScene(items)                 // replace the arrangement
studio.shareUrl()                            // a link that reopens it exactly
await studio.generate('a brass desk lamp')   // text to 3D, into the room
studio.viewInYourSpace(src, title)           // open the hosted launch page for one model
await studio.startCamera()                   // needs a user gesture on iOS
await studio.enterAR()                       // best AR path for this device
await studio.placeInYourSpace()              // native viewer (Quick Look / Scene Viewer)
await studio.toggleImmersive()               // enter or leave WebXR specifically
await studio.openRoom()                      // returns the room code
studio.destroy()                             // releases camera, socket and GPU context
```

### Events

`studio.on(name, fn)` returns an unsubscribe function. The same events also fire as
`ar-studio:<name>` DOM events on the mounted element.

| Event | Detail |
| --- | --- |
| `add` | `{ placement, remote
3dai-agentsararcorearkitaugmented-realitygithub-pagesglbgltfjavascriptmcpmodel-context-protocolquick-lookscene-viewertext-to-3dthree-wsthreejsweb-componentswebarwebxr

What people ask about 3D-AR-Studio

What is nirholas/3D-AR-Studio?

+

nirholas/3D-AR-Studio is mcp servers for the Claude AI ecosystem. Drop a full augmented-reality studio into any web page. Place any number of 3D models in your real room through the camera, generate new ones from a text prompt, arrange them, then share the scene as a link, a QR code, or a live room. WebXR + Quick Look + Scene Viewer, a free CC0 model library, and an MCP server for agents. It has 2 GitHub stars and its last recorded update is dated 2026-08-19.

How do I install 3D-AR-Studio?

+

You can install 3D-AR-Studio by cloning the repository (https://github.com/nirholas/3D-AR-Studio) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is nirholas/3D-AR-Studio safe to use?

+

Our security agent has analyzed nirholas/3D-AR-Studio and assigned a Trust Score of 95/100 (tier: Verified). See the full breakdown of passed checks and flags on this page.

Who maintains nirholas/3D-AR-Studio?

+

nirholas/3D-AR-Studio is maintained by nirholas. The last recorded GitHub activity is dated 2026-08-19, with 0 open issues.

Are there alternatives to 3D-AR-Studio?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy 3D-AR-Studio to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: nirholas/3D-AR-Studio
[![Featured on ClaudeWave](https://claudewave.com/api/badge/nirholas-3d-ar-studio)](https://claudewave.com/repo/nirholas-3d-ar-studio)
<a href="https://claudewave.com/repo/nirholas-3d-ar-studio"><img src="https://claudewave.com/api/badge/nirholas-3d-ar-studio" alt="Featured on ClaudeWave: nirholas/3D-AR-Studio" width="320" height="64" /></a>

More MCP Servers

3D-AR-Studio alternatives