List your agent

R3

MCP server● Hosted · onlinev3.195.0

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

Reviews

No review yet. Used R3? Be the first to help others choose.

What it does

R3 is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version3.195.0
PriceNot in the registry
First seen26 Sept 2026
Last checked2m ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 5h ago (live check)

Hosted endpoint

  • https://mcp.r3js.org/mcp streamable-http

In Claude Code: claude mcp add --transport http r3-1 https://mcp.r3js.org/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "r3-1": {
      "url": "https://mcp.r3js.org/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 5h ago

ONLINE R3 answered an MCP connection on 16 Nov 2026 and introduced itself as r3 3.194.0 (MCP protocol 2025-06-18).

80 tools offered to AI assistants

  • 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 its pretraining, and code written from tool descriptions alone saves cleanly and t
  • 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 1) r3_docs_read("PHYSICS_USAGE.md") colliders, rigid bodies, joints r3_docs_rea
  • 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's plan (its name and how many live projects it allows and uses: going live need
  • 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, music transport and OrbitControls (anyone who opens it can turn and zoom the view)
  • 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 project the user names ("my slot machine") rather than giving an id is found: search
  • 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 this before writing any code for a project, and after any tool call whose outcome
  • 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 the project public; making a new one is free. It is how the user sees what you b
  • 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 link is what blocks an r3_project_delete the user asked for: a preview link is t
  • 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 the user asked for it. Changing the project does NOT change the live site; r3_publ
  • 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 for it. Other people open a live project, so one that blocks an r3_project_dele
  • 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 the trash (restorable for 7 days). Also says whether the project has saved chang
  • 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 be live; this never uses a plan slot. A release in the trash or one marked incom
Show 68 more
  • 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 / not tested), the SEO title and description that search engines and link preview
  • 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 they are). Only when the user asked for it, or approved the text: these setting
  • 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 at once in the project's live copy (every open R3 tab shows it). The public addr
  • r3_project_remix · 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 acc
  • 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 to clean up your own abandoned attempts; the user's own projects and other agent
  • 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 a mesh plus geometry plus material plus colour, already connected. Call this bef
  • 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 (mesh + geometry + material + colour, already connected), so you never assemble c
  • r3_code_write · Add or replace a Code component: JavaScript a project runs. It runs on ONE event you choose (`event`): RENDER_BEFORE (default) every frame, for movement (held keys: this.keysPressed); KEY_DOWN / KEY_UP once per press / release; MOUSE_CLICK,
  • 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 is there. Use it before replacing a script, so an edit builds on the real source
  • 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 the editor and in the live portal alike, so whoever opens your preview link can
  • 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 in the project's live copy: every R3 tab with the project open shows it now, no
  • 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; this gives you the values behind them. Pass SEVERAL entityRefs in one call — tellin
  • 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 lowest and highest point, centre, size and footprint. Use it to place something ON a
  • 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 parents applied. Name a Mesh, or the root Empty of a Blender model (r3_blender_
  • 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 references set before it is created. Kept at once in the project's live copy: every
  • 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 is just focused (never reloaded). It is how the user gets to see the project you
  • 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 debug live behaviour. It needs a tab with the project open (r3_editor_open open
  • 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 project open shows it now, no editor needed and nothing to save. Name the component
  • 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 open runs the new code now, no editor needed and nothing to save. Name it with
  • 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 tab with the project open shows it now, no editor needed and nothing to save
  • 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 geometry … — with its values and references set before it is created, kept at o
  • 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 `confirm`: it returns the plan and changes nothing — the selected components, what onl
  • 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 it at once in any R3 tab that has the project open. Use it when your own change w
  • 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 scripts go back to that version (each script as a new version on top of the curren
  • 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 own click does — a paused simulation resumes. Use it to TEST what you built: run i
  • 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 own click does. Stopping physics puts every body back where it was placed. It stop
  • 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. Call it after a visual change (r3_editor_set, r3_editor_create, r3_editor_code …) t
  • 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 the showcase show, used when the project is next published (r3_publish_live, or
  • r3_entity_list · 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 sho
  • r3_entity_read · 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 co
  • r3_entity_save_template · 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
  • r3_entity_import · 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
  • r3_entity_update · 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.
  • r3_entity_assign · 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, {"ty
  • r3_component_rename · Rename a component: its entityRef, the name scripts address it by (this['name'] / this.name), and its display name when that is where the entityRef came from. Name it by entityRef or componentId. Without planId it only PLANS and changes not
  • r3_module_list · 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 show
  • r3_module_read · 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. ve
  • r3_module_write · 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, ap
  • r3_module_usage · 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
  • r3_module_pin · 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 pr
  • 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 objects land in the scene, how many meshes and materials, its screenshot, and any PEN
  • 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 object becomes an R3 Mesh keeping its own position, rotation, scale and origin,
  • 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 question: choice update_projects without reportId shows which projects and entity templ
  • 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 Entity, entityRef, part count) and its delete plan. It changes nothing: which copy
  • 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 name, so "monster-truck.blend" adds a version to the user's monster-truck model,
  • 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-time download ticket (5 minutes) and the download endpoint (URL, method, Authori
  • 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's Blender page shows it as a 3D preview they can orbit. A draft is not a saved v
  • 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 account's own artwork — a wood grain, a logo, a skybox — and then point a texture at
  • 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 sound the account already has — a footstep, a drum hit, a music bed — and then point
  • 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 a checkerboard, a gradient, a test grid or a noise tile and then actually put it
  • 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 by R3 from a procedural recipe (seeded noise, stones, bricks …). Nothing is uploa
  • 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 editable source). The account's own sets, or anyone's public one. To change a set, r
  • r3_texture_update · Change a texture set the account owns: its look (controls: seed, scale, colours, contrast, bumpiness, roughness {min, max}, metalness, size, tileWorldSize, height, applied to the set's own recipe; `scale` multiplies its pattern, so 2 is twi
  • 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 `aoMap` + `roughnessMap` + `metalnessMap` (for a set without metal its blue channel
  • r3_sound_create · Make a sound (a 48 kHz WAV in the account's audio files) from a recipe that R3 renders: layers of synth / fm / noise / sample sources, each with an envelope and effects (filter, distortion, bitcrush, delay, reverb, compressor, tremolo), and
  • r3_sound_read · Read the RECIPE a sound was made from (the editable source), with its name, url, duration, whether it loops and the sound it was edited from. The account's own sounds, or anyone's public one; an uploaded file has no recipe. To change a soun
  • r3_sound_update · Change a sound the account owns: overrides {seed, duration, channels} applied to its own recipe, or a whole new `recipe` (read the current one with r3_sound_read, change it, pass it here; r3_docs_read("SOUND_RECIPES.md") has the format). Th
  • r3_song_read · 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, wit
  • r3_song_update · 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, re
  • 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, biggest first, and the total. The same report as the R3 app's Settings → Storage, by t
  • 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 texture sets (kind textureSet: the set and its maps, r3_texture_create made it) —
  • r3_asset_share · Show one of the user's OWN images, audio files or texture sets in the R3 Community, or hide it again: the same switch as 'Show in Community' in the R3 app. public: true makes it visible to every R3 member, who can then find it in the Commun
  • 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 of the user's support issues, which only the user and R3's team see. Use it whe
  • 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 project and whether an agent filed it (and which), each with its link. It shows w
  • 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 — plus the user's OWN suggestions still awaiting R3's approval, marked pending, an
  • 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 user: an item the user already voted for stays voted, and this never removes a vote
  • 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 public, not votable, until then. r3_roadmap_list shows whether an item already cove
  • 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 help updated (with versions), components added, deleted or restored, the project

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Version3.195.0DECLAREDSRC-001 Official MCP Registry2m ago
Hosted endpointhttps://mcp.r3js.org/mcpDECLAREDSRC-001 Official MCP Registry2m ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry2m ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry2m ago
Websitehttps://r3js.orgDECLAREDSRC-001 Official MCP Registry2m ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry2m ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry2m ago

Change history

  • VERSION16 Nov 2026
    3.194.0 → 3.195.0
  • VERSION15 Nov 2026
    3.193.0 → 3.194.0
  • VERSION15 Nov 2026
    3.192.0 → 3.193.0
  • VERSION15 Nov 2026
    3.191.0 → 3.192.0
  • VERSION14 Nov 2026
    3.190.0 → 3.191.0
  • VERSION14 Nov 2026
    3.189.0 → 3.190.0
  • VERSION14 Nov 2026
    3.188.0 → 3.189.0
  • VERSION14 Nov 2026
    3.187.0 → 3.188.0
  • VERSION14 Nov 2026
    3.186.0 → 3.187.0
  • VERSION13 Nov 2026
    3.185.0 → 3.186.0
  • VERSION13 Nov 2026
    3.184.0 → 3.185.0
  • VERSION13 Nov 2026
    3.183.0 → 3.184.0
  • VERSION11 Nov 2026
    3.182.0 → 3.183.0
  • VERSION10 Nov 2026
    3.181.0 → 3.182.0
  • VERSION10 Nov 2026
    3.180.0 → 3.181.0
  • VERSION10 Nov 2026
    3.179.0 → 3.180.0
  • VERSION10 Nov 2026
    3.178.0 → 3.179.0
  • VERSION10 Nov 2026
    3.177.0 → 3.178.0
  • VERSION10 Nov 2026
    3.176.0 → 3.177.0
  • VERSION09 Nov 2026
    3.175.0 → 3.176.0
  • VERSION09 Nov 2026
    3.174.0 → 3.175.0
  • VERSION09 Nov 2026
    3.173.0 → 3.174.0
  • VERSION09 Nov 2026
    3.172.0 → 3.173.0
  • VERSION09 Nov 2026
    3.171.0 → 3.172.0
  • VERSION09 Nov 2026
    3.170.0 → 3.171.0
  • VERSION09 Nov 2026
    3.169.0 → 3.170.0
  • VERSION09 Nov 2026
    3.168.1 → 3.169.0
  • VERSION09 Nov 2026
    3.168.0 → 3.168.1
  • VERSION08 Nov 2026
    3.167.0 → 3.168.0
  • VERSION08 Nov 2026
    3.166.0 → 3.167.0

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run R3? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor R3Launch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of R3?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/r3-1?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/r3-1/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about R3

How do I connect R3?

Use the hosted endpoint https://mcp.r3js.org/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does R3 offer?

When Electra Index connected on 16 Nov 2026, it listed 80 tools: r3_docs_list, r3_docs_read, r3_whoami, r3_project_create, r3_project_list, r3_project_load, r3_preview_create, r3_preview_remove and more. The full list is in "Live check" above.

Is R3 online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 5h ago.