DocsClaude Code and Codex
Claude Code and Codex, in Angelo
Since 1.0.2, Claude Code and Codex can use Angelo over MCP: read your scene, make edits, start renders and hand Angelo's own agent a task, while Angelo is open on your computer. Their changes wait for your approval in Angelo.
Connect an app#
- Open Preferences ▸ AI Providers and scroll to External AI apps (MCP).
- Next to Claude Code or Codex, click Connect Claude Code or Connect Codex. Angelo adds one entry named
angeloto that app's MCP settings for your user, and turns on Allow apps on this computer to reach Angelo. - Start a new Claude Code or Codex session. Angelo's tools are there.
In Codex, name Angelo
Codex loads Angelo's tools only when a request looks for them. Mention Angelo or Blender when you ask, for example “in my Angelo scene, add a stone bridge”, or Codex may not use Angelo at all. Claude Code always has Angelo's tools.
For Claude Code, Angelo uses Claude Code's own claude mcp add; for Codex it adds an [mcp_servers.angelo] entry to ~/.codex/config.toml and keeps a backup of the file. Nothing else in those settings changes. When an app isn't found, or its settings can't be changed safely, Copy setup copies an MCP entry (in JSON) for you to paste in yourself; Codex's file uses TOML, so it has to be rewritten there. A pasted entry for an app Angelo didn't connect gets read-only access, and you also have to turn on Allow apps on this computer to reach Angelo yourself. Connect is the way to give an app full access.
The connection is private to your computer: each app gets its own key, and Angelo opens no network port. Keep Angelo running while you use it from the app: when Angelo is closed, or Allow apps on this computer to reach Angelo is off, the app's call answers that Angelo isn't running or that access is off, and works again once you open Angelo and retry.
What a connected app can do#
| The app can | How |
|---|---|
| Look at your scene | Inspect objects, search, read properties and see the 3D view. |
| Edit it | With Angelo's checked tools, the same ones the chat uses. |
| Render, bake and export | As background jobs, which ask you first. |
| Run Python | Every script is shown to you, with its code, before it runs. |
| Hand Angelo a task | Angelo's own agent does it, on your Angelo connection, and reports back. |
It can't read or write your files, use Generative AI, Generation Flows or your team's library, or change Angelo's settings.
Your approvals stay in Angelo#
Each app works in its own chat in Angelo, titled External: claude-code or External: codex, which starts in Approve for me: checked edits apply, and scripts and jobs wait for you. In Manual mode, the status bar says when an app is waiting; click it to open that chat. In Director, look for its chat in the chat title menu. An app can never approve, decline or change the setting itself, and Always allow scripts never applies to it. You can stop it and undo its changes as in any chat.
The app's own tool calls cost you nothing in Angelo; a task handed to Angelo's agent runs on that chat's connection, your own subscription, key or team.
Disconnect#
Disconnect on the app's row removes the angelo entry from the app and deletes its key. Turning Allow apps on this computer to reach Angelo off closes the connection for every app at once. Your organization can turn the whole feature off.
Blender MCP is something else#
Blender's own MCP add-on is separate. Angelo doesn't include or manage it; it runs its own server and runs Python outside Angelo's approvals, snapshots and Undo. The two can be installed side by side, and connecting Angelo leaves an app's Blender MCP entry alone.