FreakoutAI Launches MCP for AI-Powered Room Editing

FreakoutAI now supports MCP connections for iCommerce rooms, letting merchants connect Claude, Codex and other MCP clients to preview and save scoped room edits.

The walkthrough below runs the loop end to end: a prompt in an MCP client, a draft previewed in the Room Editor, and a saved room a visitor can walk through.

FreakoutAI now supports MCP connections for iCommerce rooms, giving merchants a direct way to bring Claude, Codex and other MCP clients into the Room Editor.

With Freakout MCP, an AI client can inspect an approved room, understand the scene structure, work with shop media, prepare visual changes, preview a draft in the editor, and save changes only after the merchant approves the direction.

The result is a more natural text-to-room workflow for immersive commerce. Instead of asking an AI tool to drive the browser by clicking around the interface, merchants can connect an MCP client to a scoped room workspace and ask for the outcome they want.

How These Rooms Were Built

None of the rooms in this article began as a 3D project. Each one began as a floor plan.

Two came from estate-agent listings on Rightmove, both in Monmouth. 4 St John Street is a floor-plan study of a three-bedroom town house, laid out as three floors side by side with the courtyard and garden office included. Almshouse is a three-bedroom mid-terrace cottage from a listing in the same town.

The third is an apartment. Grand Angle – Apt 26 is a four-room flat on level 06 of Bâtiment A at 87-89 Avenue Mermoz in Lyon, with 87.08 m² of living space and a 28.89 m² terrace, built from the developer's Promogim plan dated 2021-07-19.

A plan is a thin brief, and it is worth being plain about what survives the trip. Published room dimensions guide the scale and the layout follows the drawing. Wall heights and thicknesses, fittings, and the placement of garden elements are approximate.

That is still the interesting part. The input was a flat drawing of the kind every property listing and every developer brochure already publishes. The output is a space someone can walk through in a browser, and the work in between happened as a conversation in the Room Editor, with a preview before each save.

Property details belong to the listing agents, and listings come down once a property sells.

A Room Editor Built for AI Collaboration

Room editing is visual and iterative.

A merchant may want to move products, adjust lighting, create a display layout, add annotations, or generate a new 3D asset from a short prompt. To help with that work, an AI assistant needs context: what is in the room, what media is available, what can be changed, and what the merchant wants to review before saving.

MCP gives the assistant that context while keeping the merchant in control.

The Room Editor remains the place where the merchant reviews, saves and publishes work. The new MCP connection turns it into a shared workspace where human direction and AI execution can happen in the same flow.

What Freakout MCP Can Do

An approved MCP client can read the current room, list available shop media, upload room assets, preview unsaved drafts, and save room changes.

Depending on the permissions selected during approval, the client can also create private rooms and generate images or 3D assets within a credit limit set by the merchant.

That opens up practical workflows such as:

• Ask an assistant to redesign a product display.
• Preview a lighting or layout change before saving it.
• Use existing product images and 3D models from the shop.
• Generate a new asset inside an approved credit budget.
• Create a private workspace room for an account-level connector.

The connection is intentionally scoped. A room connection reaches the room the merchant approved. An account-level connector creates or reuses a private workspace room for that client and shop. It does not open access to every existing room in the account.

Connect Claude, Codex or Another MCP Client

For clients that ask for a single MCP URL, use the account connector:

https://freakout.ai/api/mcp/account

Each client names this differently. In Claude it is a connector: open Add custom connector and paste the URL into MCP server URL. In Codex it is an MCP: open Plugins, select the MCPs tab, choose Add, then set the type to Streamable HTTP so the client expects a remote URL rather than a local launch command.

For a specific room, open the saved room, select Agent access, copy the setup prompt, and paste it into the MCP client.

The prompt includes the room URL, the MCP server URL, and command examples for clients such as Claude Code and Codex CLI.

OAuth is the preferred setup path. The copied prompt contains no secret. The MCP client opens a browser sign-in, FreakoutAI shows the consent screen, and the client stores and refreshes its own tokens.

Preview First, Save Second

Freakout MCP is designed around preview-first editing.

A client can prepare a draft and show it in the open editor before anything is saved. If the idea works, the merchant can ask the client to commit the change.

This matters because immersive room work is not only about producing a technically valid update. It has to look right. The merchant should be able to inspect the result visually, reject it, refine it, or save it when it matches the brief.

If the merchant has unsaved local edits, FreakoutAI will not silently overwrite them with agent changes. The review loop stays visible.

Safety and Control

OAuth keeps bearer tokens out of chat transcripts, terminal history and model context. The client stores and refreshes the tokens, while the merchant approves the request in FreakoutAI.

Connections can be revoked from the Room Editor. Every request rechecks the user, shop, room, connection status and token audience before a tool runs.

Generation requires an approved credit budget, and the client cannot buy credits, change subscriptions or publish a room.

That balance is the point: AI clients can help build immersive commerce experiences faster, but the merchant stays in control of access, spend and what gets saved.

Getting Started

Open a saved iCommerce room and select Agent access, or connect through the account MCP URL:

https://freakout.ai/api/mcp/account

The full setup guide is available in the FreakoutAI documentation:

https://freakout.ai/docs/freakout-icommerce/mcp-client-setup

How to Add the Connector

There are two ways in. Use the account connector when the client only asks for a server URL, and the room connection when you are already in a saved room and want the client to work in that one.

Account connector

Add this server URL in the MCP client:

https://freakout.ai/api/mcp/account

1. Start the client's authentication flow.
2. Sign in to FreakoutAI if the browser asks.
3. Choose the shop the agent may use.
4. Review the permission controls.
5. Select Allow.

FreakoutAI creates a private workspace room for that client and shop. Reconnecting the same client in the same shop returns it to that room while the connection is still valid.

Room connection

1. Open the saved room in the Room Editor.
2. Select Agent access in the top toolbar.
3. Copy the setup prompt.
4. Paste the prompt into the MCP client.
5. Run the command shown in the prompt if the client is not configured yet.
6. Authenticate the server from the client.
7. Approve the browser request in the Room Editor.
8. Ask the client to read the room before it changes anything.

Command line

Use the server name and URL from the copied prompt:

claude mcp add --transport http freakout-room-abc123 https://freakout.ai/api/mcp/rooms/<roomId>

codex mcp add freakout-room-abc123 --url https://freakout.ai/api/mcp/rooms/<roomId>
codex mcp login freakout-room-abc123

In Claude Code, use /mcp, choose the Freakout server, then select Authenticate.

What you are approving

The consent screen controls what the client may do. Edit this room lets it read room data, preview drafts and save changes. Agent has write permission lets it save and create new private rooms. Allow Agent Spend lets it generate images and 3D assets within the credit limit you select.

To revoke access, open Agent access in the Room Editor and disconnect the agent. The current token stops working immediately and refreshes fail.