AI and coding assistants

AI is optional. Learn the manual edit/test/correct loop first. Enterprise has two authoring entry points: an external assistant using MCP and generation inside Studio.

Connect your external assistant

In Workspace Studio, select the draft and source implementation you want to work on. Save any edits you want the assistant to see.
Open Connect your assistant. Confirm the selected workspace, draft, saved version and source shown in the panel.
Use Copy endpoint to obtain that installation’s MCP address. Add it as an authenticated Streamable HTTP server in your assistant. The panel also offers Copy configuration, but client configuration formats differ.
Configure authentication through the client’s supported sign-in flow or its secure bearer-credential settings, using the authority and audience supplied by the installation operator. The copied URL configuration alone does not authenticate the client.
Use Copy starting request for the selected source. Ask the assistant to inspect saved context, show proposed changes, test accepted edits and use the actual result when correcting a failure.

Access follows the identity’s exact tenant/workspace permissions. Unsaved editor changes are excluded from saved context. Draft authoring and development tests do not grant release or publication access.

Saved code, literal imports and schemas can become assistant context; test tools can return actual records. Your assistant’s inference account determines where that information goes. Use synthetic material first and review the proposed edits.

Studio AI setup

AI setup shows the operator-configured inference routes for the workspace. Select an available route/model and review its limits. Save settings persists that selection. It does not establish that a provider is working.

Test connection is a separate inference action: it can consume provider tokens and tests the displayed selection without saving it. The connection check sends no workspace code. Do not use it when you only intend to inspect settings.

The gateway must be reachable from the Enterprise server. A route labelled local does not prove that its gateway has no hosted fallback; confirm routing with the operator. Do not paste raw provider credentials into source code or shared notes.

Provider integration is experimental and has not yet been validated end to end. Arrange provider testing with your installation operator. LiteLLM is the first integration target, with local inference retained and OpenRouter following. The manual authoring workflow remains available without inference.

Which MCP guide applies?

Interface	Scope
Enterprise authoring MCP	Authorized saved drafts, source context, edits and development tests in Enterprise. Use the connection panel above.
Complete MCP	The Windows desktop app’s browser/workspace tools, approval and audit controls. See Complete MCP.
Remote Ops	A separate control interface for standalone Complete/Node hosts. It is not an Enterprise MCP connection.

For availability problems, use troubleshooting. For the planned authoring workflow, see the roadmap.