Connect ChatGPT to 3dCMS

ChatGPT can drive 3dCMS through the same hosted connector Claude uses: a URL, https://3dcms.info/mcp, and a Google sign-in. Nothing to install, no token to paste. ChatGPT calls custom MCP servers from developer mode, which OpenAI offers on paid ChatGPT plans.

Add the connector

1. Turn on developer mode

   In ChatGPT on the web, open Settings, find the apps and connectors section, open its advanced settings and switch on Developer mode. OpenAI moves and renames these menus from time to time; if yours look different, search ChatGPT's help for "developer mode".

2. Create a connector

   Create a new connector, call it 3dCMS, and give it the URL https://3dcms.info/mcp. Choose OAuth for authentication if it asks. 3dCMS registers the client on its own, so there is no client id or secret to fill in.

3. Sign in with Google

   ChatGPT opens the 3dCMS sign-in in your browser. Use the same Google account you use for 3dCMS (a new account is created the first time, free, no credit card) and approve the access. chatgpt.com is on the sign-in's list of approved clients, so the handoff back to ChatGPT should go straight through.

4. Turn it on in a chat

   In a new chat, pick developer mode from the tools menu and enable the 3dCMS connector. The thirteen 3dcms tools should now be available to the model.

What to ask first

Start small so you can see the round trip work:

• "List my 3dCMS scenes." On a new account the answer is an empty list, which is fine: it proves the sign-in worked.
• "Make a 3dCMS scene called Studio with a home page that says my name in big letters, an about page a few metres away, and a sign linking them."
• "Take a screenshot of Studio and review the design."
• "Publish Studio." ChatGPT gets a notice of what publishing means and has to ask you before it goes live.

The full ten-minute version is in Your first 3D website from a chat.

What to expect

• Every result carries an editorUrl. Open it in your browser while signed in to 3dCMS and the scene is there to inspect and keep editing by hand.
• ChatGPT may ask before each change. In developer mode ChatGPT can ask you to confirm tool calls that write. That is ChatGPT's own safety step, separate from 3dCMS's publish confirmation, and it is worth keeping.
• Read the tool reference before a big build. The apply_ops tool carries a long description of what it can build. If the model guesses at field names, ask it to read the operations reference in the apply_ops tool first; it gets better results when it does.
• Screenshots show up in the chat. get_scene_screenshot returns a real render, and ChatGPT draws it as a picture card under its reply (a "Rendering the scene" notice shows while the server works, then the image replaces it). The model sees the same image, so it can judge the shot and fix the scene with apply_ops. If the card stays blank, check that ChatGPT's apps advanced settings have CSP enforcement for custom apps turned on, then ask for the screenshot again.

The limits

• A paid ChatGPT plan. Custom MCP connectors live in developer mode, which is not on the free ChatGPT plan.
• No paid generation. The hosted connector has the thirteen core tools. generate_3d and generate_material spend credits, so they run from the editor or the local server, not from a connected app.
• Render budget. Server-side screenshots come out of a daily budget: 10 a day on the free 3dCMS plan, more on the paid ones (see Tools & quick phrases).
• Publishing always asks. Nothing goes public until you say yes in the chat.
• Plan limits are stated, not sold. When your 3dCMS account hits a cap (scenes, storage, the render budget, or the publish weight limit), ChatGPT is told plainly that the account has reached a plan limit and that it is managed at 3dcms.info. It gets no pricing or upgrade link, because OpenAI's rules for apps forbid them inside ChatGPT. To raise a limit, open Membership & plan limits in your browser.