Connect an agent

Run a non-Store Fanta build and focus an open design. A source build uses cargo run; the non-Store app binary is /Applications/Fanta.app/Contents/MacOS/fanta when installed there.
Choose Help → Connect Claude Code / Codex… in Fanta. It copies commands for the running app executable and its user data directory. Run the Claude command from the project directory, or put the Codex snippet in that project's .codex/config.toml. For example, an app installed at /Applications/Fanta.app produces this command shape:
```
claude mcp add --scope project --transport stdio fanta -- '/Applications/Fanta.app/Contents/MacOS/fanta' '--mcp-stdio' '--user-data-dir' '<copied Fanta data directory>'
```
Codex (.codex/config.toml in the project):
```
[mcp_servers.fanta]
command = "/Applications/Fanta.app/Contents/MacOS/fanta"
args = ["--mcp-stdio", "--user-data-dir", "<copied Fanta data directory>"]
```
Restart the client, check /mcp, and call get_editor_state. The live server exposes thirteen tools. Keep Fanta running with the intended design open.

fanta_live_mcp.enabled defaults to true in Fanta user settings. Setting it false turns the local server off. The bridge checks that the discovered app process is alive, so a stale socket-discovery file after an unclean quit does not count as a connection. Copy the command again when the Fanta executable or user data directory changes. See Troubleshooting.

These steps are verified for non-Store builds. The Mac App Store feature build prevents Fanta from launching local command-backed MCP servers as a client, while remote HTTP servers remain supported. That restriction is separate from the inbound live canvas server; the packaged Store bridge has not been verified. See Settings and build differences.