External agents can safely control Objo Studio through MCP

Objo Studio can safely expose its live solution, editor, and project state to external coding agents through the Model Context Protocol (MCP).

A user enables the optional External Agents (MCP) feature in Settings, pairs a named MCP client, and copies a one-time configuration into their external agent (for example Codex, Claude Code, or VS Code). The agent can then discover a running Studio instance, read the live solution and document text, consult the bundled Objo documentation, make version-checked source edits that stay unsaved and fully undoable, compile the active project, explicitly save, and optionally run or stop the active project.

Access is off by default and read-only by default. Every mutation is permission-checked, recorded in a local activity view, and undoable through Studio. The user can revoke a paired client or disable all external access entirely from Studio at any time, without using the external agent. Studio never opens a network listener, and no tool can read or write arbitrary files, execute a caller-selected process, or obtain credentials.