R3

インストール

使っているAIアプリを選んで、設定をコピーしてください。

チェック 2/3 合格 · 質問内容は提供元のサーバー（mcp.r3js.org）を通ります · ✓ コマンド確認済み 2026年11月13日

claude mcp add --transport http --scope user r3 https://mcp.r3js.org/mcp

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

{
  "servers": {
    "r3": {
      "type": "http",
      "url": "https://mcp.r3js.org/mcp"
    }
  }
}

使えるアプリ

このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。

インターネット経由でつなげるアプリ

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

すべてのアプリと長所・短所 →

できること

ツールの名前と説明は、サーバーが2026年11月10日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

• 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 then silently does nothing. r3_docs_read

• 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_read("HOWTO_PHYSICS.md") one task step by s

• 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 needs one), and whether the R3 platform is r

• 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) — ready for components to be added. Pass

• 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 for it; its projectId is what r3_projec

• 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 was reported as unknown, to see what ac

• 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 built. Takes the projectId returned by r3

• 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 temporary, so it may then be removed with

• 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_publish_live does: on a project that is alre

• 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_delete goes offline only once the user has b

• 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 changes that are not live yet: saving does NO

• 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 incomplete is refused. Nothing is deleted: 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 / not tested), the SEO title and description that search engines and link previews show, how the live page starts (Start

• 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 settings shape the PUBLIC live page — its title

• 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 address does not change: a preview or live l

• 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 account's own. The files it uses are copied

• 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 agents' are refused. With project:delete:owne

• 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 before r3_factory_run if you are unsure of

• 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 components by hand. Kept at once in the p

• 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, SWIPE, MUSIC_BEAT, PHYSICS_COLLISION on

• 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 instead of overwriting it blind, and af

• 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 read them. This is the built-in surface

• 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 editor needed and nothing to save (r3_e

• 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 — telling six similarly-named materials apart is

• 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 terrain: an object stands on the ground

• 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_import makes one, named " _root"), and t

• 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 tab with the project open shows it n

• 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 are working on, and how a tab gets the

• 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 opens one). r3_component_read reads the kept

• 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 with componentId or entityRef. `values`

• 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 componentId or entityRef and pass baseVe

• 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_factory_list lists the factories an

• 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 once in the project's live copy: every R3

• 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 only they use (their geometry, material, co

• 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 was wrong or the user asks you to take it

• 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 current one), and the name. The user sees it a

• 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 it, then look with r3_editor_capture 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 own click does. Stopping physics puts every body back where it was placed. It stops every project open in that tab. Change

• 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 …) to check what you built, and after r3_edi

• 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 Publish update in the editor). The edit

• 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 shows one template's members and versions;

• 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 code modules it imports, and its recent ve

• 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). Without templateId it updates the template the Entity was imported from (or makes a new one, under the Entity's id); asNew: tr

• 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 until r3_component_set sets started: tr

• 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.g. a moved ship keeps its position), scr

• 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, {"type": "Mesh"}, or both). Each one's value

• 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 nothing: it checks the new name (refused: n

• 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 shows one's code; r3_module_write creates or

• 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. version reads an older version. A long mod

• 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, api}; } };`. It runs once per run with `th

• 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 import a public module of yours are only

• 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 project's module of that name). The pin li

• 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 PENDING update (a re-upload that changes me

• 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, with its geometry, materials and texture

• 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 templates use an older version (or an earlier

• r3_blender_copies

  Does this project hold the same Blender model more than once (two whole imports side by side)? Answers "N copies of : … Keep one?" with each copy (its Entity, entityRef, part count) and its delete plan. It changes nothing: which copy stays is the user's choice, and the other is r

• 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, or makes the model. A tool argument can

• 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, Authorization header); the response body is the

• 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 version: one draft per user, the newest w

• 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 it with r3_component_set. Search by name

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月14日にチェック

• ! 注意

  作者とリポジトリが一致

  レジストリにソースのリポジトリが載っていないため、公開者（r3js.org）とコードを照合できません

• … 未チェック

  今もメンテナンスされている

  このリポジトリはまだGitHubから読み取っていません

• … 未チェック

  ライセンスがある

  このリポジトリはまだGitHubから読み取っていません

• ✓ 合格

  エンドポイントが応答する

  1413ミリ秒で応答（HTTP 200）

• – 対象外

  OAuthでサインイン

  サインイン不要

• ✓ 合格

  ツールの説明に隠れた指示がない

  60件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

ユーザーレビュー

まだレビューはありません

Google でログインしてレビューを書く

デザイン・画像・音声のほかのサーバーとの比較i

• このカテゴリのほかの3042件のうち0%よりスターが多い
• このカテゴリのほかの3042件のうち97%より最近レジストリに公開
• 基本チェックの結果が、このカテゴリのほかの3042件のうち50%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

同じカテゴリのほかの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：↓ 週あたりのダウンロードi★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

Figma Context MCP

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

作者：GLips·広く使われている·↓ 15.2万/週·★ 1.6万·5 か月前更新

パソコンで動く

インストール

AutoClip

Clip long videos into short clips with covers and captions. Local CLI and MCP.

作者：zhouxiaoka·広く使われている·↓ 205/週·★ 1万·17 日前更新

パソコンで動く

インストール

Next AI Draw.io

draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand

作者：DayuanJiang·広く使われている·↓ 2.2万/週·★ 3.7万 リポジトリ全体のスター·今日更新

パソコンで動く

インストール

作者のREADME

リポジトリにREADMEが見つかりません