# R3js R3 MCP server

Source: https://glimind.com/server/mcp-registry%2Forg.r3js%2Fr3
Registry id: `mcp-registry/org.r3js/r3`
Status: live (checked 2026-10-26T22:31:52.329Z)

## Measurements (30 days)

- Uptime: 99.84%
- Checks: 2534
- Outages (90 days): 4

## Install

```json
{
  "mcpServers": {
    "r3js-r3-mcp-server": {
      "type": "http",
      "url": "https://mcp.r3js.org/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http r3js-r3-mcp-server https://mcp.r3js.org/mcp
```

## Tools (61)

- `r3_asset_delete`: Delete one of the account's images, models, audio files, Blender models (kind blender: a whole uploaded .blend with every version; its meshes in use stay) or te
- `r3_assets_unused`: The account's images, models and audio files that nothing uses — no project, no entity template, no other user's project — with each one's size and date, bigges
- `r3_audio_list`: List the audio files this R3 account owns, with the URL to use for each one. That URL is exactly what R3ComponentAudio.url takes, so this is how you find a soun
- `r3_blender_copies`: Does this project hold the same Blender model more than once (two whole imports side by side)? Answers "N copies of <model>: … Keep one?" with each copy (its En
- `r3_blender_download`: Get a .blend of one of the user's OWN Blender models (from r3_blender_list) to open in Blender: the current version, or the version fileId names. Answers a one-
- `r3_blender_draft_push`: While you build a model in Blender for the user, push an APPLIED copy of your working .blend after each step (body done, wheels done, materials done): the user'
- `r3_blender_import`: Add a Blender model the account has uploaded (its current version) to an existing R3 project — the whole model, or only the meshes you name. Every Blender mesh 
- `r3_blender_list`: List the Blender models this R3 account has uploaded — one per .blend file name, the current version of each — with what it will produce: how many Blender objec
- `r3_blender_update`: A re-uploaded Blender model is always its latest version; the user's projects keep the meshes they have until asked. This tool asks and answers that one questio
- `r3_blender_upload`: Save a .blend you made or changed (in Blender, through a Blender MCP) as the newest version of one of the user's Blender models: the model is named by the file 
- `r3_bug_report`: Send R3 a bug report about R3 ITSELF (the engine, the editor, these tools), in the user's name and naming you (your agent key or app connection). It becomes one
- `r3_bug_reports_mine`: The user's own support issues — bug reports and questions they or their agents (agent keys and app connections) sent R3 — newest first, with status, date, the p
- `r3_code_read`: Read back what a Code component actually contains — its full JavaScript source and the event it runs on. r3_code_write reports what it wrote; this reports what 
- `r3_code_write`: Add or replace a Code component: JavaScript that makes a project DO something. It runs on ONE event you choose (`event`): RENDER_BEFORE (default) every frame, f
- `r3_component_add`: Add one component of ANY registered type — a collider, a rigid body, a joint, a light, a material, a geometry … — to a saved R3 project, with its values and ref
- `r3_component_bounds`: The size and place of meshes and imported models, in R3 units (metres): the world-space box around each (min, max, size, centre), the mesh's scale, rotation and
- `r3_component_read`: Read back what components actually hold — a material's colour and roughness, a mesh's position, which material it uses. r3_project_load gives you the names; thi
- `r3_component_set`: Set one or more properties on a component that already exists in a project — a material's roughness, a mesh's position, which material a mesh uses. Kept at once
- `r3_docs_list`: Every R3 document this server can give you, IN READING ORDER, with what each one covers and how big it is. R3's documentation begins here: no model has R3 in it
- `r3_docs_read`: Return one R3 document in full, or one API symbol. Paths come from r3_docs_list: r3_docs_read("CODE_PATTERNS.md") how a Code component is written (reading order
- `r3_editor_add_component`: The same tool as r3_component_add (this is its older name): add one component of ANY registered type — a collider, a rigid body, a joint, a light, a material, a
- `r3_editor_capture`: Capture the canvas of a project open in the user's R3 editor — the scene as it looks NOW, running physics included — and LOOK at it: the answer is an image. Cal
- `r3_editor_code`: The same tool as r3_code_write (this is its older name): replace a Code component's code, kept at once in the project's live copy: every R3 tab with the project
- `r3_editor_create`: The same tool as r3_factory_run (this is its older name): add an object — a cube, sphere, light, physics body … — kept at once in the project's live copy: every
- `r3_editor_delete`: Delete components from the project the user has OPEN in their R3 editor, exactly as the editor's delete dialog asks it — in TWO calls. First call WITHOUT `confi
- `r3_editor_inspect`: Read what components hold RIGHT NOW in an R3 tab that has the project open: runtime values included — a moving body's position while the project runs. Use it to
- `r3_editor_open`: Open a project in the R3 editor the user has open in their browser (their most recently used R3 tab) and focus it, so they see it. A project already open there 
- `r3_editor_run`: Press the Run buttons of the user's open R3 editor: start physics, code, audio and music (all of them, or the ones named in `systems`), exactly as the user's ow
- `r3_editor_set`: The same tool as r3_component_set (this is its older name): change properties of a component, kept at once in the project's live copy: every R3 tab with the pro
- `r3_editor_set_preview_image`: Use what the project's camera shows NOW, in the user's open R3 editor, as the project's share image: the picture its live page, link previews (social cards) and
- `r3_editor_stop`: Press the Stop buttons of the user's open R3 editor: stop physics, code, audio and music (all of them, or the ones named in `systems`), exactly as the user's ow
- `r3_editor_undo`: Undo the last change YOU (this agent key or app connection) made to a project: everything one of your tool calls changed is undone together, and the user sees i
- `r3_factory_list`: List the R3 factories available to r3_factory_run, with each one's options, types and defaults. A factory builds a complete, correctly-wired object — a cube is 
- `r3_factory_run`: Add an object to an existing R3 project — a cube, sphere, terrain, lighting, a physics body, and so on. Each factory builds a complete, correctly-wired object (
- `r3_help_write`: Set the instructions that ship WITH a project — controls, what to press, what it does. R3 renders them in a modal behind a floating "?" button and the H key, in
- `r3_image_create`: Store a small image YOU generated in this R3 account's image library and get back the URL for it — the value R3ComponentTexture.url takes. This is how you make 
- `r3_image_list`: List the images this R3 account owns, with the URL to use for each one. That URL is exactly what R3ComponentTexture.url takes, so this is how you find the accou
- `r3_preview_create`: Create a shareable preview link for a saved R3 project, so a person can open it in a browser and see it running. The link is valid for 7 days and does NOT make 
- `r3_preview_remove`: Remove the preview link of an R3 project: every preview link to it stops working at once (teammates' too). Only when the user asked for it, or when the preview 
- `r3_project_changes`: What OTHER people changed in a project — the user in any R3 tab, their other agents — oldest first, grouped per author and per thing: properties set, code and h
- `r3_project_create`: Create a new R3 project and save it to the user's account. Produces a complete, openable project — scene, world, camera, renderer, lighting, audio listener, mus
- `r3_project_delete`: Permanently delete an R3 project. With the project:delete:created right (on by default), only a project YOU created (this agent key or app connection) — use it 
- `r3_project_list`: List the projects this R3 account can work on — its own and its teams' — last updated first, with the projectId every other project tool takes. It is how a proj
- `r3_project_load`: List the components in an existing R3 project — what it contains and, for each one, its entityRef: the name code addresses it by (`this['mesh_cube_1']`). Read t
- `r3_project_rename`: Rename a project: the name shown in the user's project list, the editor's title and the live page. The same change as clicking the title in the R3 editor, kept 
- `r3_publish_live`: Publish an R3 project live: makes a RELEASE (a frozen copy) of the project as it is now and makes it the one its public live URL shows, for anyone. Only when th
- `r3_publish_settings_read`: Read the publish settings of one of the user's own R3 projects in this environment — what the app's Deploy → Settings shows: Works on (keyboard / touch / both /
- `r3_publish_settings_set`: Change publish settings of one of the user's own R3 projects in this environment — the app's Deploy → Settings. Only the settings named change (the rest stay as
- `r3_release_list`: List the releases of an R3 project, newest first: number, date, who made it, note, size, which one is LIVE (what the public URL shows), pinned, and releases in 
- `r3_release_restore`: Put a project's working copy back the way one of its releases (saved versions) had it: components added since are removed, removed ones come back, values and sc
- `r3_release_rollback`: Make an earlier release of a live R3 project the one its public URL shows again (rollback, or forward again). Only when the user asked for it. The project must 
- `r3_roadmap_list`: The public R3 roadmap: what is planned, in progress, proposed by the community and shipped, with each item's vote count and whether the user has voted for it — 
- `r3_roadmap_suggest`: Suggest a feature for R3's public roadmap, in the user's name and naming you (your agent key or app connection). It is HELD until R3's team approves it: not pub
- `r3_roadmap_upvote`: Add the user's vote to a public roadmap item (its id from r3_roadmap_list), when the user wants it or it covers what you were about to suggest. One vote per use
- `r3_terrain_height`: How high the ground of a heightfield terrain is at the world (x, z) positions you ask, exactly as physics and the drawn terrain have it, plus the terrain's lowe
- `r3_texture_apply`: Wire a texture set to a material in a project: the colour map to `map`, the normal map to `normalMap`, the ambient-occlusion / roughness / metalness map to `aoM
- `r3_texture_create`: Make a matching, seamlessly tiling texture SET for a material: a colour map, a normal map and a packed ambient-occlusion / roughness / metalness map, rendered b
- `r3_texture_read`: Read one texture set: its name, size, tile size, the three map urls, the numbers its render measured, the sets it was edited from, and the full RECIPE (the edit
- `r3_texture_update`: Change a texture set the account owns: its look (controls: seed, scale, colours, contrast, bumpiness, roughness {min, max}, size, tileWorldSize, height, applied
- `r3_unpublish_live`: Take a live R3 project offline: its public live URL stops working at once, and the live-project slot it used on the plan is free again. Only when the user asked
- `r3_whoami`: Report the R3 account you act for, how you are connected (an agent key, or an app connection made with Sign in with R3), what you are allowed to do, the account

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.