Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

R3

REMOTE · MCP.R3JS.ORG

Build 3D web apps: physics, audio, music, Blender import. Live edits, undo, versions, publishing.

Available components

0 this week 94 Trust /100

Last scanned (7 hours ago)

Scores higher than 99% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security97
Transport & Reachability100
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 27868 tokens (~238/item across 117 items; 80 tools + 37 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management98
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 19 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (98% of tools); any adoption earns full credit.Pass
Tool Safety97
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 7 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "r3_publish_settings_read" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 82 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Server version: 3.222.0 → 3.223.0 functional
    • Server version: 3.221.0 → 3.222.0 functional
    • Server version: 3.220.0 → 3.221.0 functional
  • 20 Nov 26 0
    • Server version: 3.219.0 → 3.220.0 functional
    • Server version: 3.218.0 → 3.219.0 functional
  • 19 Nov 26 0
    • New resource “HOWTO_TEXT.md” functional
    • Server version: 3.217.0 → 3.218.0 functional
    • Server version: 3.216.0 → 3.217.0 functional
    • Server version: 3.215.0 → 3.216.0 functional
    • Server version: 3.214.0 → 3.215.0 functional
    • Server version: 3.213.0 → 3.214.0 functional
    • Server version: 3.212.0 → 3.213.0 functional
    • Server version: 3.210.0 → 3.212.0 functional
    • Server version: 3.208.0 → 3.210.0 functional
  • 18 Nov 26 0
    • Server version: 3.207.0 → 3.208.0 functional
    • Server version: 3.206.0 → 3.207.0 functional
    • Server version: 3.205.0 → 3.206.0 functional
    • Server version: 3.204.0 → 3.205.0 functional
    • Server version: 3.202.0 → 3.204.0 functional
    • Server version: 3.200.0 → 3.202.0 functional
    • Server version: 3.199.1 → 3.200.0 functional
  • 17 Nov 26 0
    • Server version: 3.198.1 → 3.199.1 functional
    • Server version: 3.197.0 → 3.198.1 functional
    • Server version: 3.196.0 → 3.197.0 functional
  • 16 Nov 26 0
    • Resource “HOWTO_GAMES.md” was removed ▼ functional
    • Server version: 3.195.0 → 3.196.0 functional
    • Server version: 3.194.0 → 3.195.0 functional
  • 15 Nov 26 0
    • Server version: 3.193.0 → 3.194.0 functional
    • Server version: 3.192.0 → 3.193.0 functional
    • Server version: 3.191.0 → 3.192.0 functional
  • 14 Nov 26 0
    • New resource “HOWTO_GAMES.md” functional
    • Server version: 3.190.0 → 3.191.0 functional
    • Server version: 3.188.0 → 3.190.0 functional
    • Server version: 3.186.0 → 3.188.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.r3js.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.r3js.org CN=YE2,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA384 67f99411823edf75d7cbcba072a4f7d33c6
SANs: mcp.r3js.org
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.r3js.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
r3js.org. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="r3", resource_metadata="https://mcp.r3js.org/.well-known/oauth-protected-resource/mcp", scope="project:read project:write code:write editor:dispose editor:run project:delete:created asset:read asset:write publish:preview support:write roadmap:suggest roadmap:vote"

Bearer realm="r3", resource_metadata="https://mcp.r3js.org/.well-known/oauth-protected-resource/mcp", scope="project:read project:write code:write editor:dispose editor:run project:delete:created asset:read asset:write publish:preview support:write roadmap:suggest roadmap:vote"
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY

Protected resource metadata

Document https://mcp.r3js.org/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.r3js.org/mcp
Authorisation server https://mcp.r3js.org

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.r3js.org/mcp Verified 200
http (plaintext) http://mcp.r3js.org/mcp HTTPS enforced 301 https://mcp.r3js.org/mcp
MCP tools · 80 exposed · ~23,934 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
r3_entity_assign ~338

Put many components of a project into one Entity in a single change, instead of r3_component_set {"entity": …} once per component. Name them in members (entityRefs or ids), or let match find them ({"prefix": "ship1_"} on the entityRef, {"type": "Mesh"}, or both). Each one's value components (position, rotation, scale, colours) follow it, as with r3_component_set; a component in another entity moves (the plan says from where). Without planId it only PLANS and changes nothing: the members, what follows each, what a match skipped (Entities and project infrastructure never join one) and what is refused (not found, a name several components share, two members that would share one entityRef inside the entity). With that planId it applies the plan as ONE undoable change every open R3 tab sees, writing only the entity of each, all or nothing: if anything it touches changed since, nothing is written and the new plan is returned.

NameTypeReqDescription
entitystringyesThe Entity to put them in: its entityRef or id (r3_project_load lists it).
matchobject–Find the components instead of naming them: prefix, type, or both (both must hold).
membersarray–The components to put in it, by entityRef or id. Or use match.
planIdstring–The plan being applied, from this tool without planId (same members / match). Leave it out to plan.
projectIdstringyesThe project, from r3_project_load.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
applicablebooleanyes–
appliedbooleanyes–
changesintegeryes–
createdarrayyes–
entityobjectyes–
environmentstringyes–
membersarrayyes–
planIdstringyes–
projectIdstringyes–
refusalsarrayyes–
seq–yes–
skippedarrayyes–

No examples provided.

r3_entity_import ~222

Put a copy of an entity template (this account's, or a public one) into a project: every member with fresh ids, its positions and colours as saved, bound to a new Entity that starts DORMANT (started: false: its code, sounds and physics wait until r3_component_set sets started: true), or awake with started: true (its code, sounds and physics run at once). The copy remembers the template and version it came from. version imports an older version. Answers the new Entity's entityRef and its members' entityRefs. r3_editor_undo takes it back.

NameTypeReqDescription
projectIdstringyesThe project to put the copy into.
startedboolean–true: the copy runs at once (code, sounds, physics). Default false: dormant, woken later with r3_component_set {started: true}.
templateIdstringyesThe template (r3_entity_list shows its templateId).
versioninteger–A version to import (default: the current one).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
entityIdstringyes–
entityRefstringyes–
membersarrayyes–
projectIdstringyes–
seqnumber|nullyes–
startedbooleanyes–
templateIdstringyes–
valueComponentCountnumberyes–
versionnumber|nullyes–

No examples provided.

r3_entity_list ~167

List this R3 account's entity templates: reusable bundles (a ship, a lamp post) saved from an Entity in a project, each with its current version and member count. community: true lists everyone's public templates instead. r3_entity_read shows one template's members and versions; r3_entity_import puts a copy into a project; r3_entity_save_template saves an Entity of a project as a template.

NameTypeReqDescription
communityboolean–true lists the PUBLIC templates of every user instead of this account's own.
cursorstring–Continue a list: the nextCursor of the previous page.
limitinteger–How many (default 25, max 100).
searchstring–Only templates whose name matches, searched across all of them.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
filterstringyes–
hasMorebooleanyes–
nextCursorstring|nullyes–
templatesarrayyes–

No examples provided.

r3_entity_read ~175

Read one entity template (this account's, or a public one): its current version, the members of the version read (type, name, entityRef; value components such as positions and colours are counted, they belong to their member), the shared code modules it imports, and its recent versions with their notes. version reads an older version, and the references its members hold to components outside the Entity (outsideReferences: infrastructure such as the scene or camera is expected and re-bound on import; anything else is left empty by an import into another project). The current version is the baseVersion r3_entity_save_template needs to update the template.

NameTypeReqDescription
templateIdstringyesThe template (r3_entity_list shows its templateId).
versioninteger–A version to read (default: the current one).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
controlsstringyes–
descriptionstringyes–
importsarrayyes–
isPublicbooleanyes–
membersarrayyes–
namestringyes–
notestringyes–
outsideReferencesarrayyes–
ownerstring|nullyes–
readVersionnumber|nullyes–
templateIdstringyes–
valueComponentCountnumberyes–
versionnumber|nullyes–
versionsarrayyes–
yoursbooleanyes–

No examples provided.

r3_entity_save_template ~541

Save an Entity of a project as an entity template version: its members (the components bound to it, with the positions, rotations and colours they hold), a description and a picture. `description` is required (20..1000 characters): write it from the Entity's components and its code, in plain words for someone browsing templates: what it is, what it does when the project runs, and how to use it (what to add it to, what it needs). `controls` (optional, at most 200 characters) names its keys or buttons, e.g. "Arrow keys drive, Space brakes". The picture: after the save, any open R3 tab of the account renders the template alone (framed on it, as authored, nothing running) and keeps it as the template's picture. With no R3 tab open the save is kept and the picture is pending: R3 takes it the next time the user opens the Entities Browser. Without templateId it updates the template the Entity was imported from (or makes a new one, under the Entity's id); asNew: true always makes a new template. Updating an existing template needs baseVersion, the version read with r3_entity_read: if the template changed since, nothing is saved and the answer names the current version. The project itself is not changed. The answer lists every reference a member holds to a component outside the Entity (outsideReferences): infrastructure (scene, world, camera, listener, renderer, transport) is expected and re-bound on import; anything else (a geometry or material left outside) is listed first, because an import into another project leaves it empty. The save is not refused for them.

NameTypeReqDescription
asNewboolean–true saves a NEW template, never updating one.
baseVersioninteger–The template version you read (r3_entity_read): required to update an existing template.
controlsstring–Optional, at most 200 characters: its keys or buttons, e.g. "Arrow keys drive, Space brakes".
descriptionstringyesRequired, 20..1000 characters, plain words: what it is, what it does when the project runs, how to use it. Written from the Entity's components and code.
entityRefstringyesThe Entity (its entityRef, or its id).
notestring–What changed, kept with the version.
projectIdstringyesThe project holding the Entity.
templateIdstring–The template to update (default: the one the Entity came from, else a new one).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
memberCountnumberyes–
namestringyes–
outsideReferencesarrayyes–
pictureobjectyes–
templateIdstringyes–
valueComponentCountnumberyes–
versionnumberyes–
versionCreatedbooleanyes–

No examples provided.

r3_entity_update ~266

Bring the copies of an entity template in this account's projects up to its newest version. Without reportId it only reports, per project: what the template changed that the project did not (taken), what the project changed itself (kept, e.g. a moved ship keeps its position), scripts changed on both sides (kept: code is never merged), parts the template added, and parts it removed (kept unless removeGone: true). With that reportId it applies the report to the projects, as undoable changes every open editor sees; if anything moved since, nothing is changed and the new report is returned. projectIds limits it to those projects (default: every project holding a copy). Published releases never change. Applying needs the template:update right.

NameTypeReqDescription
projectIdsarray–Only these projects (default: every project of the account holding a copy).
removeGoneboolean–Also remove the parts the newest version no longer has (default false: kept and listed). Plan with it and apply that report with it.
reportIdstring–The report being applied, from this tool without reportId. Leave it out to plan.
templateIdstringyesThe template (r3_entity_list shows its templateId).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
appliedbooleanyes–
environmentstringyes–
namestringyes–
projectsarrayyes–
removeGonebooleanyes–
reportIdstringyes–
templateIdstringyes–
toVersionnumberyes–
updatedarrayyes–

No examples provided.

r3_factory_list ~102

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 a mesh plus geometry plus material plus colour, already connected. Call this before r3_factory_run if you are unsure of a factory name or its options.

NameTypeReqDescription
factorystring–Optional: return only this factory, e.g. "Cube". Omit for all of them.

No output schema declared.

No examples provided.

r3_factory_run ~431

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 (mesh + geometry + material + colour, already connected), so you never assemble components by hand. Kept at once in the project's live copy: every R3 tab with the project open shows it now, no editor needed and nothing to save (r3_editor_create is the same tool). The answer says what was kept and its seq. "name" names what you make ("Leg front left" → entityRef leg_front_left): the primary component (a cube's Mesh, a light), unique in the project (a name already used gets _2); its geometry and material take it too (leg_front_left_geometry, leg_front_left_material). Name parts when you make them (a later rename: r3_component_rename). "StudioLighting" lights a scene the way a photo studio does: one of R3's built-in HDR environments (studio, sunset, sky) as the scene's environment, so metal and glossy materials reflect, plus a key light. Use r3_factory_list to see the factories and their options.

NameTypeReqDescription
factorystringyesFactory name, e.g. "Cube", "Sphere", "PhysicsCube". See r3_factory_list.
namestring–The name of what you make, e.g. "Leg front left" (at most 120 characters). Its entityRef, the name code uses, follows from it (leg_front_left).
paramsobject–Factory options, e.g. {"color": 16711680, "position": {"y": 2}}. Every option has a default. Color is a packed RGB integer. Rotations are in RADIANS, not degrees: a quarter turn is Math.PI/2 ≈ 1.5708…
projectIdstringyesThe project to add to, from r3_project_create.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
componentCountnumberyes–
creatednumberyes–
factorystringyes–
physicsarrayyes–
projectIdstringyes–
rolesobjectyes–
seq–––

No examples provided.

r3_help_write ~374

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 the editor and in the live portal alike, so whoever opens your preview link can read them. This is the built-in surface for that, so a Code component needs no overlay of its own. The body is markdown — headings, bullets, `code`, links: the controls as a player needs them, e.g. "## Controls\n\n- `Space` — jump". A project has ONE help. Call this again and it replaces the text rather than adding a second. REPLACING needs baseVersion, the codeVersion r3_component_read gave for the Help: text is never merged, so a write on an older version is refused with the current text. The first Help needs none. The optional title is the modal's heading ("Controls", "How to play"); leave it out to keep "Help". Kept at once in the project's live copy: every R3 tab with the project open shows it now. The result gives you the component's entityRef — pass that to r3_component_set to change the trigger key, move or hide the button, or have the help open automatically on load.

NameTypeReqDescription
baseVersioninteger–REQUIRED when the project already has a Help: its codeVersion, from r3_component_read. Leave it out for the first Help.
markdownstringyesThe help text, as markdown. Replaces whatever is there.
projectIdstringyesThe project to write into, from r3_project_create or r3_project_load.
titlestring–Heading shown at the top of the modal, e.g. "Controls". Default "Help".
NameTypeReqDescription
actionstringyes–
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
codeVersionintegeryes–
componentIdstringyes–
entityRefstringyes–
namestringyes–
projectIdstringyes–
seq–––
titlestringyes–
warningsarray––

No examples provided.

r3_image_create ~368

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 a checkerboard, a gradient, a test grid or a noise tile and then actually put it on something with r3_component_set. Pass the image as a base64 data URL (data:image/png;base64,…), up to 1MB decoded. PNG, JPEG, GIF and WebP are stored; PNG is the right choice for a generated pattern. This is NOT a way to upload an image file you already have. You would have to emit every byte of it as base64, which for a real texture is far more output than a reply can hold — and this server cannot read your disk. A person uploads real artwork in the R3 app, and r3_image_list shows what they have already put there: the account's own artwork, where there is some, beats a generated substitute. Each call stores a NEW image, so calling it twice with the same bytes leaves two rows. The name you give is what appears in the owner's Images browser, prefixed with "agent-" so they can tell where it came from; a descriptive one says what it is. For a material's texture set (colour + normal + roughness that tile), use r3_texture_create instead: R3 renders it, so no bytes go through you.

NameTypeReqDescription
dataUrlstringyesThe image, as data:image/png;base64,… — up to 1MB once decoded.
namestringyesA short plain-language name, e.g. "checkerboard 512". Stored as agent-checkerboard-512.png and shown to the account owner, so describe what the image IS.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
filenamestringyes–
imageIdstring|nullyes–
mimeTypestringyes–
sizeBytesnumberyes–
urlstring|nullyes–

No examples provided.

r3_image_list ~312

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 account's own artwork — a wood grain, a logo, a skybox — and then point a texture at it with r3_component_set. Search by name rather than paging: search: "wood" is matched against every image on the account by the server, not against the page you happen to be holding. Each row says whether it is a "texture" (an ordinary image for a material slot) or an "environment" map (.hdr / .exr). Those two are not interchangeable: an environment map belongs on Scene.environment, Scene.backgroundTexture or MaterialStandard.envMap, and renders as garbage in an ordinary map slot. You cannot upload an existing image file from here — a tool argument is JSON, this server cannot read your disk, and a real texture is megabytes. A person uploads those in the R3 app. r3_image_create is the one exception: it takes a small image you generated yourself, such as a checkerboard or a gradient.

NameTypeReqDescription
cursorstring–Continue a previous listing: pass the nextCursor it returned, unchanged. Omit for the first page.
limitinteger–How many to return (default 25, max 100).
searchstring–Match this text against the file names, on the server. Omit for everything.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
hasMorebooleanyes–
imagesarrayyes–
limitnumberyes–
nextCursorstring|nullyes–
searchstring|nullyes–

No examples provided.

r3_module_list ~134

List this R3 account's shared code modules: named pieces of script stored once (e.g. "ship-core") that any Code component in any project imports with `const core = this.import('ship-core')`. Each with its latest version. r3_module_read shows one's code; r3_module_write creates or changes one; r3_module_usage says where it is used. See the how-to "HOWTO_CODE_MODULES.md".

NameTypeReqDescription
cursorstring–Continue a list: the nextCursor of the previous page.
limitinteger–How many (default 25, max 100).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
hasMorebooleanyes–
modulesarrayyes–
nextCursorstring|nullyes–

No examples provided.

r3_module_pin ~189

Choose which version of a shared code module ONE project runs: version n pins it (the project keeps that version when the module changes), version null follows the latest again. moduleId names someone else's PUBLIC module (it is then the project's module of that name). The pin lives in the project's import map, not in the code: no script changes. Open editors of the project reload. A release (go-live) freezes the versions the project runs at that moment anyway. Not taken back by r3_editor_undo: pin again.

NameTypeReqDescription
moduleIdstring–Someone else's public module (its id from r3_module_read); omit for your own.
namestringyesThe module name the project's scripts import, e.g. "ship-core".
projectIdstringyesThe project.
version–yesThe version to pin, or null to follow the latest.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
mapobjectyes–
modulesarrayyes–
projectIdstringyes–

No examples provided.

r3_module_read ~293

Read one shared code module: its code, its version (the baseVersion r3_module_write needs), the latest version, its notes, and how many of this account's projects use it. Your own module by name; someone else's PUBLIC module by moduleId. version reads an older version. A long module is read in PAGES (at most 60000 characters each): every answer gives totalChars, the sha256 of the WHOLE code, and truncated / nextOffset. When truncated is true you have only part of it: read on with the same name, the version answered and offset = nextOffset, join the pages, and check the sha256 before you write it back (half a module written back deletes the rest).

NameTypeReqDescription
lengthinteger–How many characters to read at most (default and maximum 60000; 8000 in an R3 Builder session). A page ends on a whole line when it can.
moduleIdstring–Instead of name: a module id (someone else's public module).
namestring–Your module's name, e.g. "ship-core".
offsetinteger–Where to start reading, in characters (default 0). For the next page pass the nextOffset of the previous answer.
versioninteger–A version to read (default: the latest). Pass it when reading the next page.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
codestringyes–
createdAtstring|nullyes–
createdBystring|nullyes–
descriptionstringyes–
isPublicbooleanyes–
latestVersionnumberyes–
lengthnumberyes–
moduleIdstringyes–
namestringyes–
nextOffsetnumber|nullyes–
notesstring|nullyes–
offsetnumberyes–
ownerstringyes–
sha256stringyes–
totalCharsnumberyes–
truncatedbooleanyes–
usedInProjectsnumber|nullyes–
versionnumberyes–
yoursbooleanyes–

No examples provided.

r3_module_usage ~85

Which of this account's projects (and entity templates) import one of your code modules: per project the scripts that import it, the version it runs, and whether that version is pinned or follows the latest. Projects of other accounts that import a public module of yours are only counted.

NameTypeReqDescription
namestringyesYour module's name, e.g. "ship-core".
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
latestVersionnumberyes–
moduleIdstringyes–
namestringyes–
otherAccountsnumberyes–
projectsarrayyes–
templatesarrayyes–

No examples provided.

r3_module_write ~506

Create a shared code module (baseVersion 0) or write its next version (baseVersion = the version you read). The code is a FUNCTION BODY that returns the exports, e.g. `return { createShip(host, config) { … return {start, update, dispose, api}; } };`. It runs once per run with `this` undefined (it reaches no component: the importing script passes in what it needs) and the same globals as a script (Event, EntityManager, THREE, GraphicsThree). Variables at its top level are shared by every script that imports it; per-instance state goes in what its factory returns. A module cannot import another module. A write on an older version is refused with the current code, never merged. Projects that follow the latest version run the new one at once (open editors reload it); pinned projects and published releases keep their version. PATCH a long module instead of sending all of it: replacements [{old, new, count?}] with baseVersion and baseSha256 (the version and sha256 r3_module_read answered), no code. They apply in order, each on the text the previous one left; each old must occur exactly count times (default 1), else nothing is saved and the answer names the replacement and how many it found. At most 200 replacements and 60000 characters of old + new text per call. See "HOWTO_CODE_MODULES.md".

NameTypeReqDescription
baseSha256string–With replacements only: the sha256 r3_module_read answered for baseVersion (of the WHOLE code).
baseVersionintegeryes0 to create the module; otherwise the version r3_module_read answered (with replacements: the version they apply to, which must be the latest).
codestring–The whole module: a function body that returns its exports object (at most 250000 characters; comments and readable names are fine). Omit it when you send replacements.
descriptionstring–What the module is for (one line).
namestringyesThe module name: lower-case letters, digits and hyphens, e.g. "ship-core".
notesstring–What changed in this version (shown in the version list).
replacementsarray–Instead of code: exact replacements on version baseVersion, in order (at most 200, 60000 characters of old + new in all).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
createdbooleanyes–
moduleIdstringyes–
namestringyes–
occurrencesnumber|nullyes–
replacementsnumber|nullyes–
sha256stringyes–
totalCharsnumberyes–
unchangedbooleanyes–
versionnumberyes–

No examples provided.

r3_preview_create ~198

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 the project public; making a new one is free. It is how the user sees what you built. Takes the projectId returned by r3_project_create. Where the client shows MCP Apps (Claude on the web, desktop and mobile), the preview also shows as a playable card right in the chat, under this answer: use it when the user asks to see or play the project here or in the chat. When an R3 tab has the project open, the project's picture (its card and the link's image) is refreshed from that tab; when none has, the picture refreshes the next time the project is opened in R3.

NameTypeReqDescription
projectIdstringyesThe project id, as returned by r3_project_create.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
cameraControlsboolean|nullyes–
cardobject––
environmentstringyes–
expiresInHoursnumberyes–
pictureOutdatedbooleanyes–
pictureRefreshedbooleanyes–
previewUrlstringyes–
projectIdstringyes–
slugstringyes–

No examples provided.

r3_preview_remove ~156

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 link is what blocks an r3_project_delete the user asked for: a preview link is temporary, so it may then be removed without a separate request, and the user is told it was removed. A live project stays live; a project that was only previewed is no longer published. Deletes nothing: r3_preview_create makes a new link. A project with no open preview link is refused and left as it is. Needs the publish:preview right.

NameTypeReqDescription
projectIdstringyesThe project id (r3_project_list).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
environmentstringyes–
livebooleanyes–
previewRemovedbooleanyes–
projectIdstringyes–

No examples provided.

r3_project_changes ~279

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 help updated (with versions), components added, deleted or restored, the project renamed. Your own changes are never listed. Every answer about a project already ends with a short "Since your last call" line; this is its full list. Without `since`: from where you last looked (and moves that mark to now, unless advance: false). The mark belongs to your agent key or app connection, not to the conversation: two conversations on one share it. With `since` (a seq, e.g. the one the "+N more" line names, or 0 for everything still in the log): from there, without moving anything. Needs project:read.

NameTypeReqDescription
advanceboolean–Without since: move your mark to now (default true). false reads without moving it.
limitinteger–At most this many groups, the newest (default 50, at most 200); the rest are counted.
projectIdstringyesThe project (r3_project_list).
sinceinteger–List from this seq on (the "+N more" line names it; 0 = everything the log still holds).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
firstbooleanyes–
fromSeqintegeryes–
groupsarrayyes–
moreintegeryes–
projectIdstringyes–
toSeqintegeryes–
totalintegeryes–
unreadintegeryes–

No examples provided.

r3_project_create ~349

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, music transport and OrbitControls (anyone who opens it can turn and zoom the view) — ready for components to be added. Pass `template` for a phone project (mobile-portrait / mobile-landscape) that fills the screen when published. Returns the project id, which every other project tool takes. r3_whoami confirms which account it is created in.

NameTypeReqDescription
cameraobject–Where the project's camera starts and what it looks at, e.g. framing a model you add next. Omit it for the default: (0, 5, 10) looking at the origin.
namestring–Project name, shown in the user's project list. Defaults to "Untitled Project". Max 120 characters.
templatestring–Start from a project template instead of an Empty Project. "mobile-portrait" — A phone held upright: designed at 390×844 (~19.5:9), fills the screen when published. "mobile-landscape" — A phone held…
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
componentCountnumberyes–
environmentstringyes–
namestringyes–
projectIdstringyes–
templatestring––

No examples provided.

r3_project_delete ~301

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 to clean up your own abandoned attempts; the user's own projects and other agents' are refused. With project:delete:owned, any project the user owns, and only when the user asked for it: pass owned: true for a project you did not create (an app connection is then asked for that right). A published project (live, or with an open preview link) is refused: it must be taken offline first. If the refusal is for a preview link (temporary, 7 days), it may be removed without a separate request (r3_preview_remove) and the delete tried again; the user is then told it was removed. If the project is live, other people can open it: it goes offline only once the user has been asked and agreed, never as a step of the delete. This is irreversible: there is no trash and no undo.

NameTypeReqDescription
ownedboolean–true when the project is one of the user's own, not one you created: it needs project:delete:owned. Only when the user asked to delete it. Leave out for a project you created.
projectIdstringyesThe project id to delete: one you created, or (with project:delete:owned) any project the user owns.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
deletedbooleanyes–
environmentstringyes–
projectIdstringyes–

No examples provided.

r3_project_list ~280

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 project the user names ("my slot machine") rather than giving an id is found: search for it; its projectId is what r3_project_load takes. Search by name rather than paging: search: "slot" is matched (case-insensitively, anywhere in the name) against EVERY project by the server, not against the page you are holding. Names are not unique: when more than one project matches, the candidates' name, team and last save tell them apart, and which one is meant is the user's answer. Each row says whose space it is in (personal, or a team by name), the account's role on it (a viewer cannot save changes), whether it is in the R3 Community, and whether you (this agent key or app connection) created it.

NameTypeReqDescription
cursorstring–Continue a previous listing: pass the nextCursor it returned, unchanged. Omit for the first page.
limitinteger–How many to return (default 25, max 100).
searchstring–Match this text against project names, on the server (case-insensitive). Omit for every project.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
hasMorebooleanyes–
limitnumberyes–
nextCursorstring|nullyes–
projectsarrayyes–
searchstring|nullyes–

No examples provided.

r3_project_load ~190

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 this before writing any code for a project, and after any tool call whose outcome was reported as unknown, to see what actually landed. Value components (Vector3, Color, Scalar) are not listed individually — reach them through their owner, e.g. `mesh.position.x`. Each object says which entity it belongs to (entity: {entityRef, id}, or null; r3_component_set {"entity": …} changes it), and an entityRef several components share (the same name in different entities) is listed with their ids: tools refuse that name, use the id.

NameTypeReqDescription
projectIdstringyesThe project to read, from r3_project_create or the R3 app.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
componentCountnumberyes–
namestring|nullyes–
objectsarrayyes–
projectIdstringyes–
valueComponentCountnumberyes–

No examples provided.

r3_project_remix ~269

Remix a project: copy the published release of a project into a NEW private project in this account. The source is a Community or live project whose author allowed remixes (for now R3's own starters and showcase projects), or one of the account's own. The files it uses are copied into the account's own lists, the new project carries a credit line naming the original and its author, and its code starts held until Run is pressed in the R3 editor. The original is not changed. Limits: 20 remixes per account in 24 hours and 5 per agent key in an hour; one remix copies at most 50.0MB of files; a project with videos cannot be remixed yet. Returns the new project id, which every other project tool takes, the credit, and notes on anything that could not be copied. r3_editor_open opens it in the user's R3 tab and r3_preview_create makes a private link to show it.

NameTypeReqDescription
namestring–The new project's name. Defaults to "<original name> (remix)", made unique in this account. Max 120 characters.
projectIdstringyesThe project to remix: its id from its R3 page, r3_project_list, or the user.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
copiedBytesnumberyes–
creditobjectyes–
environmentstringyes–
namestringyes–
notesarrayyes–
projectIdstringyes–
sourceProjectIdstringyes–

No examples provided.

r3_project_rename ~154

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 at once in the project's live copy (every open R3 tab shows it). The public address does not change: a preview or live link keeps working. Scripts are not affected (they never address the project by name). Renaming a COMPONENT is not this tool: that is done in the R3 editor.

NameTypeReqDescription
namestringyesThe new name. Leading and trailing spaces are trimmed. Max 120 characters.
projectIdstringyesThe project to rename, from r3_project_list or r3_project_create.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
changedbooleanyes–
namestringyes–
previousNamestring|nullyes–
projectIdstringyes–
seq–––

No examples provided.

r3_publish_live ~445

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 the user asked for it. Changing the project does NOT change the live site; r3_publish_live does: on a project that is already live this is a publish update (a new release replaces the live one), and the answer names the release number and what changed since the previous live release. `note` (optional, up to 500 characters) is stored with the release. `slug` (optional, the first time a project goes live) is the project part of its public address (e.g. "my-game" for …/<handle>/my-game: letters, numbers and dashes); without it R3 uses a free address (the project's name when free) and the answer says which. Once a project has been live its address never changes. Going live the FIRST time uses one of the live-project slots of the project owner's plan (an update uses none); going live needs a plan. When there is no plan or no room, nothing is published and the answer says how many live projects the plan allows, how many are used and where the user picks a plan. It publishes every change kept so far (yours and the user's: there is nothing to save first). r3_release_list shows the releases, r3_release_rollback makes an older one live again. Needs the publish:live right.

NameTypeReqDescription
notestring–Optional: what this release is, in a few words (up to 500 characters), e.g. "new cue and rules".
projectIdstringyesThe project id (r3_project_list / r3_project_create).
slugstring–Optional, first go-live only: the project part of the public address, e.g. "my-game" (letters, numbers and dashes). Without it R3 uses a free address and says which. A project that has been live keep…
NameTypeReqDescription
addressChosen–yes–
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
changes–yes–
embedCodestringyes–
environmentstringyes–
firstGoLivebooleanyes–
livebooleanyes–
liveUrlstringyes–
notestring|nullyes–
previousNumbernumber|nullyes–
projectIdstringyes–
releaseNumbernumberyes–
slugstringyes–

No examples provided.

r3_publish_settings_read ~143

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 / not tested), the SEO title and description that search engines and link previews show, how the live page starts (Start button, first click, on load), its controls and badge. Also answers a SUGGESTION for Works on, from a scan of the project's code for keyboard / touch / pointer handlers — only a suggestion. r3_publish_settings_set changes them. Needs the project:read right.

NameTypeReqDescription
projectIdstringyesThe project id (r3_project_list).
NameTypeReqDescription
addressstring|nullyes–
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
environmentstringyes–
galleryobject––
hiddenBecauseNoSourcesarray––
livebooleanyes–
portalSettingsobjectyes–
projectIdstringyes–
seoDescriptionstringyes–
seoTitlestringyes–
worksOnstringyes–
worksOnSuggestion–yes–

No examples provided.

r3_publish_settings_set ~495

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 they are). Only when the user asked for it, or approved the text: these settings shape the PUBLIC live page — its title and description in search results and link previews (seoTitle, seoDescription), Works on (keyboard puts a "made for a keyboard" note on phones and a "desktop" badge; touch a "mobile" badge; both, both; untested none — set it only after the user confirmed it or it was tested, never from the code scan alone), how it starts (with a Start button: what runs before the Start button, startButton.before {code, physics}, and whether the project's share picture shows until Start, startButton.poster shareImage), its controls. Invalid values are refused with every problem named, and nothing is saved. The answer names what changed; open live and preview pages are told (a preview reloads, a live page offers a reload). Takes effect without a new release. `address` changes the public address of a project that is or was live (only when the user asked for it): e.g. "my-game" for r3js.org/<handle>/my-game; the old address then redirects to the new one, so links already shared keep working. Refused by name when taken, invalid or not live yet (a first go-live chooses it: r3_publish_live `slug`). Needs the publish:live right. R3 admins only: `gallery` features, hides or sets the example prompt of a project in the landing gallery (any member's project; send it without `settings` for a project that is not yours).

NameTypeReqDescription
addressstring–The new project part of the live address, e.g. "my-game" (letters, numbers and dashes). Only for a project that is or was live; the old address redirects to the new one.
galleryobject–R3 admins only: the landing gallery, e.g. {"featured": true} or {"examplePrompt": "…"}.
projectIdstringyesThe project id (r3_project_list).
settingsobject–Only the settings to change, e.g. {"worksOn": "keyboard", "seoDescription": "…"}.
NameTypeReqDescription
addressobject––
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
changedarrayyes–
environmentstringyes–
galleryobject––
portalSettingsobject––
projectIdstringyes–

No examples provided.

r3_release_list ~114

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 the trash (restorable for 7 days). Also says whether the project has saved changes that are not live yet: saving does NOT change the live site; r3_publish_live does. Read-only. Needs the project:read right.

NameTypeReqDescription
projectIdstringyesThe project id (r3_project_list).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
changesNotLiveboolean|nullyes–
livebooleanyes–
liveReleaseNumbernumber|nullyes–
projectIdstringyes–
releasesarrayyes–

No examples provided.

r3_release_restore ~272

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 scripts go back to that version (each script as a new version on top of the current one), and the name. The user sees it at once in any R3 tab that has the project open. Only when the user asked for it. Two steps: WITHOUT planToken it changes nothing and says what restoring would change, with a planToken; the same call WITH that planToken, once the user has seen the plan and agreed, restores. If the project changed in between, nothing is changed and the new plan comes back. The whole restore is ONE change of yours: r3_editor_undo takes it back. It never changes which release is LIVE (what the public URL shows): that is r3_release_rollback. The release number comes from r3_release_list. Needs project:write (and code:write when scripts change).

NameTypeReqDescription
planTokenstring–The planToken the first call answered; only when the user agreed to that plan.
projectIdstringyesThe project (r3_project_list).
releaseNumbernumberyesThe release to restore the working copy to (r3_release_list).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
headSeqintegeryes–
opCountintegeryes–
planTokenstring|nullyes–
projectIdstringyes–
releaseNumbernumberyes–
restoredbooleanyes–
summaryobjectyes–

No examples provided.

r3_release_rollback ~132

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 be live; this never uses a plan slot. A release in the trash or one marked incomplete is refused. Nothing is deleted: the release that was live stays in the list. Take the number from r3_release_list. Needs the publish:live right.

NameTypeReqDescription
projectIdstringyesThe project id (r3_project_list).
releaseNumbernumberyesThe release to make live (r3_release_list).
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
changedbooleanyes–
environmentstringyes–
previousNumbernumber|nullyes–
projectIdstringyes–
releaseNumbernumberyes–

No examples provided.

r3_roadmap_list ~177

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 — plus the user's OWN suggestions still awaiting R3's approval, marked pending, and the ones R3 declined, marked declined with R3's reason (only the user sees them; neither is votable); a declined item is not suggested again. It shows whether an item already covers an idea before r3_roadmap_suggest: r3_roadmap_upvote votes for that one instead of a duplicate. Narrow it with `search` (title and description, any case) and `status`.

NameTypeReqDescription
searchstring–Words to find in the title or description, any case.
statusstring–Only items with this status.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
declinednumberyes–
itemsarrayyes–
pendingnumberyes–
totalnumberyes–

No examples provided.

r3_roadmap_suggest ~203

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 public, not votable, until then. r3_roadmap_list shows whether an item already covers it (r3_roadmap_upvote votes for that one instead). A good suggestion says what the feature lets a person do and why (what was being built when it was missed). Something broken rather than missing is r3_bug_report's. Rate-limited per agent key or app connection (a few a day). Needs the roadmap:suggest right.

NameTypeReqDescription
categorystring–Where it belongs; "other" when unsure.
descriptionstringyesWhat it lets a person do, and why it is needed.
titlestringyesOne line naming the feature, e.g. "Per-wheel tyre grip in the Inspector".
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
approvedbooleanyes–
idstringyes–
titlestringyes–

No examples provided.

r3_roadmap_upvote ~96

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 user: an item the user already voted for stays voted, and this never removes a vote. Needs the roadmap:vote right.

NameTypeReqDescription
idstringyesThe roadmap item id, from r3_roadmap_list.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
idstringyes–
titlestringyes–
voteCountnumberyes–
votedbooleanyes–

No examples provided.

r3_song_read ~157

Read a project's Song: its tracks (each plays Patterns, DrumGrids, Beats or Audio files in clips placed in bars), automation lanes (keyframes on a track's or the master's gain, pan or effect settings), sections, master chain and length, with every source as its entityRef, plus a summary and the songVersion r3_song_update takes as baseVersion. Read it before a change ("move the drop", "a slower filter sweep"). The schema: SONGS.md; the how-to: HOWTO_SONG.md.

NameTypeReqDescription
projectIdstringyesThe project, from r3_project_list.
songstring–The Song's entityRef; leave it out when the project has one song.
NameTypeReqDescription
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
bpmnumber|nullyes–
componentIdstringyes–
enabledbooleanyes–
entityRefstringyes–
namestring|nullyes–
projectIdstringyes–
secondsnumber|nullyes–
songobjectyes–
songVersionintegeryes–
songsarrayyes–
summaryobjectyes–
warningsarray––

No examples provided.

r3_song_update ~704

Change a project's Song with small typed changes, or make a new Song (create). The changes are applied in order and kept as ONE change (one undo step, every open R3 tab shows it): ops: setSong, setSections, setMaster, addTrack, setTrack, removeTrack, setClips, addClip, moveClip, removeClip, setLane, removeLane, addPoint, setPoint, removePoint, setChain, setEffect, addModulator, removeModulator, insertBars, splitClip, transposeClip, setClipGain. Tracks are named by their id ("kick"), sources by entityRef (a Pattern, DrumGrid, Beat, Audio or AudioPositional), clips and lane points by their index as r3_song_read lists them, positions in bars (bar 0 = the start). Examples: {"op": "moveClip", "track": "hats", "clip": 0, "start": 6}; {"op": "setLane", "track": "master", "target": "lp.frequency", "points": [{"bar": 0, "value": 350, "curve": "exp"}, {"bar": 12, "value": 1200}]}; {"op": "insertBars", "at": 64, "count": 8} (moves everything from bar 64 on 8 bars later); one eighth of a clip a few semitones higher, its length kept: {"op": "splitClip", "track": "bass", "clip": 0, "at": 65}, {"op": "splitClip", "track": "bass", "clip": 1, "at": 65.125}, {"op": "transposeClip", "track": "bass", "clip": 1, "semitones": 2} (whole semitones -24..24; a Sound Studio sound is rendered again from its public recipe, another file pitch-shifted, a Pattern's synth notes moved; 0 takes it off); that clip quieter (a clip's Volume in dB, -24..12, on top of its track's; 0 takes it off): {"op": "setClipGain", "track": "bass", "clip": 1, "gain": -4}. A song is version-checked, never merged: changing one needs baseVersion, the songVersion r3_song_read answered; if someone changed it since, the write is refused with the current version. A new Song (create) needs none. Every result is checked by lib-r3's song schema (SONGS.md) before anything is kept. How-to: HOWTO_SONG.md.

NameTypeReqDescription
baseVersioninteger–REQUIRED to change a song: its songVersion from r3_song_read. Leave it out with create.
changesarray–The changes, in order: [{"op": "setTrack", "track": "kick", "gain": -3}, …]. Required unless create.
createobject–Make a NEW Song (wired to the project's Transport), then apply changes to it, e.g. {"name": "Main song"}.
projectIdstringyesThe project, from r3_project_list.
songstring–The Song's entityRef; leave it out when the project has one song.
NameTypeReqDescription
actionstringyes–
answerstringyesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guida…
changedarrayyes–
componentIdstringyes–
entityRefstringyes–
namestring|nullyes–
partsobjectyes–
projectIdstringyes–
seq–––
songVersionintegeryes–
summaryobjectyes–
warningsarray––

No examples provided.

Install

How do I install the R3 MCP server?

R3 is a hosted endpoint at https://mcp.r3js.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.r3js.org

# add to Claude Code
claude mcp add --transport http org-r3js-r3 'https://mcp.r3js.org/mcp'
Common questions

What is the R3 MCP server?

R3 is an MCP server listed in the public MCP registry as org.r3js/r3. Build 3D web apps: physics, audio, music, Blender import. Live edits, undo, versions, publishing. This page covers its hosted endpoint (https://mcp.r3js.org/mcp).

Is the R3 MCP server safe to use?

R3 scores 94 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the R3 MCP server expose?

R3 exposes 80 tools: r3_docs_list, r3_docs_read, r3_whoami, r3_project_create, r3_project_list, and 75 more. Their descriptions and schemas cost roughly 23,934 tokens of context every time the server is loaded.

Does the R3 MCP server require authentication?

Yes. R3 asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the R3 MCP server still maintained?

R3 is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the R3 MCP server?

VerifyMCP ran 14 checks on R3, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.