Show a project in the user's open R3 editor
r3_editor_openOpen 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 project r3_editor_inspect reads. To show the project to the user right here in the chat, use r3_preview_create instead (a playable card in the chat where the client shows MCP Apps, else a link).
The same access rules as opening it by hand: the user's own projects, their teams', and public ones. The editor holds up to 4 projects; at that limit it refuses. Nothing is saved or changed. When no editor is open, the answer says where the user can open one.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>"
},
"name": "r3_editor_open"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | The project to open, from r3_project_list or r3_project_create. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| answer | Yes | This 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 guidance. | |
| editor | Yes | ||
| opened | Yes | ||
| focused | Yes | ||
| projectId | Yes | ||
| alreadyOpen | Yes | ||
| projectName | Yes |