Connect an external AI assistant with MCP
Use the app’s connection instructions and verify the intended project first.
On this page
What this helps you do
Use the app’s connection instructions and verify the intended project first.
When to use it
You want your external AI client to read or control the intended desktop project.
Before you begin
Use the desktop app and check the edition requirement: Basic read / Pro automation. The current published version is shown above. Confirm the selected item and playhead before changing anything. This audit does not verify a physical Windows device.
Step by step
Screenshots: Mac v1.7.0 Follow each step with the real app interface below. Select an image to enlarge the marked area.
- Open the desktop window you intend to control and choose Enable MCP. Re-enable it after restarting. Being connected alone does not mean the AI has edited anything or has editing permission.
Figure 1 The MCP switch and question-mark help in the top bar. Enable the connection, then read the app’s instructions. - Open the adjacent help button and copy its instructions into your AI client. Keep the dynamically supplied local command, args, env and path; do not reuse a Mac or Windows path from another machine. The desktop app includes its runtime. Use your client’s official reload entry.
Figure 2 The copy controls in MCP help. The instructions contain a local app path; use the text shown on your own computer. - Ask the assistant to call baimo_editor_session list/context and confirm the window, project, sceneId, revision, authorization.canAutomate and capabilities.canEdit. A valid seven-day device trial includes MCP and retains its original expiry. Do not paste a license code into the AI conversation.
Figure 3 The MCP switch and question-mark help in the top bar. Enable the connection, then read the app’s instructions. - Use target=app and sessionId, then read the revision, prepare, preview, apply and read back. Blue dots, ripple animation and task status indicate AI control; only 3D rotation and zoom remain available. Stop AI and edit invalidates the old task. A separate headless project is not the visible window; do not replace current-window editing with whole-project pushing.
Figure 4 Use current-window session plans and verify actual applied changes; stop AI to take over.
Changes in 1.6.0
This release provides 198 tools, including shared model-category moves, template listing/insertion, viewport locks, arrays and independent camera-motion ranges. Read the current window and capabilities first, then use real object/camera IDs and receipt revisions. Model import adds a library entry; instantiation is separate. A cut-only task must not move actors or retime camera motion. Hidden SI/Smart workbench interfaces are not public entry points.
Changes in 1.7.0
This release provides 198 tools, including delivery-material read/save operations. Video audio and desktop saving follow the current client entitlement and native confirmation. Paid MCP writes also stop after managed revocation or expiry. Activation-code issuance and the seller registry are not exposed to the editor MCP.
Settings and edit scope
| Control or concept | Meaning and boundary |
|---|---|
| Read / write | Status and project reads help verify the target. Automated editing and professional delivery need Pro or an active trial. |
| Launch path | The app supplies the correct local path. Do not copy a path from someone else’s computer. |
Check the result
The assistant reads the intended project and objects, and edits have an explicit target and a success result.
Troubleshooting and recovery
A side effect is not proof of tool success; inspect error results too. Internal interfaces and seller license-issuing flows are not user setup steps.
If the result is unexpected, stop playback, check the selected item and time, and use Undo before making another change. Keep a backup rather than repeatedly overwriting the project.
Open project → inspect → edit → play → save → reopen → check exportKeep learning
Include your app version, operating system and the error message. Never include your license or API key.