Connect directly (without the editor)

The default setup is the editor entry: the connector wires your editor to the Workbench, and your AI client connects to the editor. This guide is the escape hatch — connecting your client directly to the Workbench cloud server, with no editor in the loop.

Before you start

• An MCP client that supports remote HTTP servers and OAuth — or one with Agent Plugins support (one-command install below).
• No editor, connector, or UE project is required.

When to use it

• The editor is down. You want a post-crash analysis and the editor won't start, or you don't want to launch it. Crash artifacts persist on disk — logs in Saved/Logs, crash folders in Saved/Crashes — and a direct client can analyze them as files.
• CI or headless machines. No editor process exists to connect through.
• Non-UE repositories. The project isn't an Unreal Engine project at all.
• Stack recovery. You're on an experimental engine or plugin build and want a known-good connection.
• You prefer it. Some agents hold one long-lived session, and you want the Workbench on it directly.

Both entries coexist and share one account: billed tools draw from the same wallet either way.

Install the Agent Plugin

The Agent Plugin configures supported clients in one command:

# Universal installer (detects Claude Code, Cursor, Codex, VS Code, ...)
npx plugins add Tinirau/unreal-workbench

# Or, inside Claude Code:
/plugin marketplace add Tinirau/unreal-workbench

Or add the server manually

Clients without Agent Plugins support can connect directly:

• Transport: Streamable HTTP
• URL: https://mcp.spaghetti.gg/api/mcp/agentic-engine/mcp

{
  "mcpServers": {
    "workbench": {
      "url": "https://mcp.spaghetti.gg/api/mcp/agentic-engine/mcp"
    }
  }
}

On first connect, your client opens a browser window where you sign in at the portal — an account is created there with welcome credits if you don't have one. Clients that support standard MCP OAuth discovery (RFC 9728 protected-resource metadata) resolve the sign-in page on their own; beyond the URL, there's nothing to configure.

Carry team and project context

Tool calls without team context bill your personal wallet — everything works except the three project-scoped research tools. To work with team context, your client sends it as headers on every call, sourced from the Project Settings context:

{
  "mcpServers": {
    "workbench": {
      "url": "https://mcp.spaghetti.gg/api/mcp/agentic-engine/mcp",
      "headers": {
        "x-spaghetti-team": "your-team-uuid",
        "x-spaghetti-project": "your-project-uuid"
      }
    }
  }
}

In a UE project, run setup_spaghetti from your client first: it walks you through picking or creating the team and project and tells your client which values these are (the same ids land in the Spaghetti section of Config/DefaultGame.ini, so both stay in sync). The ids can also be passed with individual calls — an explicit id overrides the header.

Turn off the editor connection

If a project should use the direct entry only, stop the editor from connecting. Open Config/DefaultEditorPerProjectUserSettings.ini in the UE project and find the spaghetti entry under [/Script/MCPClientToolset.MCPToolsetSettings]:

+MCPServers=(Name="spaghetti",...)

Set bEnabled=False in that entry — the durable option: the edited entry stays in the committed file, and the connector never rewrites or re-adds it. Removing the entry also stops the connection on this machine, but it is not durable across your team: the connector's one-shot marker lives on each machine, so a fresh clone (or a new teammate's machine) with the entry missing gets it shipped again. The Workbench cloud tools keep working through your direct client either way.

Editing the project file is the supported way for a reason: deleting the entry from Editor Preferences does not stick — the preferences UI writes no counter-entry to your per-user config, so the shipped project-default row simply brings the connection back on the next editor launch.

Sign out and switch accounts

The sign-in is a persistent authorization, not a browser session — your client stays signed in until you end it. Run your client's logout command (for example claude mcp logout), or disconnect the client from the portal's Account page — see Connect your AI client.

Verify

• List the available tools. in your client returns the Workbench tools — analyze_logs, tidy_assets, make_tool, topup, and the research tools listed in the Tools reference.

Next steps

• Run your first analysis — the guided tutorial
• Teams and projects — how context routes billing
• Connect your AI client — the default editor entry