Build with AI: Claude, ChatGPT and MCP

Connect Claude to 3dCMS

Add the hosted connector by URL and sign in with Google, or run the local server with a token for the paid generation tools.

Open in the interactive manual →

The interactive version has full-text search, a table of contents, and light/dark themes.

The hosted connector (nothing to install)

Open 3dcms.info/claude: it takes you straight to 3dCMS in Claude's Connectors Directory. Click Connect.

Prefer a URL? Add a custom connector (a paid Claude plan feature) in Claude's connector settings and give it:

https://3dcms.info/mcp

Either way, Claude sends you through a normal browser sign-in, the same Google account you use for 3dCMS. Approve it once and the 3dcms tools appear in your conversation. There's no token to generate, nothing to install, and nothing to keep running on your machine.

In Claude Code the hosted connector is one command, then /mcp inside Claude Code to finish the sign-in:

claude mcp add --transport http 3dcms https://3dcms.info/mcp

Using ChatGPT or Gemini instead? See Connect ChatGPT to 3dCMS or Connect Gemini to 3dCMS. Cursor, VS Code, Windsurf, Codex or Gemini CLI? See Other MCP clients.

It's your account. The connector only ever sees the scenes belonging to the account you signed in with.
It expires and renews on its own. Access is short-lived and refreshed quietly in the background.
You can cut it off. Sign out everywhere on your Account page revokes the connector's access along with everything else.
Thirteen tools. Everything in Tools & quick phrases except generate_3d, generate_material and get_generation. Generation spends credits, and the sign-in you give a connected app covers your scenes, not your credits, so it runs from the editor or from the local server with your own API token.

3dCMS is published in the official MCP registry (as info.3dcms/mcp), and appears on Smithery and Glama, which build their listings from it, so a client that browses those directories may offer 3dCMS directly instead of asking you for the URL.

Before you sign in, a client can see the tool list but not use it. A connection with no authorization gets a normal handshake and the same thirteen tool names and descriptions, which is how a directory or a client can show you what 3dCMS offers before you have an account. Nothing can run from there: every call comes back refused, with a pointer to the sign-in. So if a client lists the tools and then fails on all of them, the browser sign-in never finished. Reconnect and complete it.

A session that went quiet starts over on its own. The hosted connector keeps a session per conversation and lets it go after two hours idle, or when the server restarts for a deploy. A call on a session it no longer holds is answered with "session expired, send a new initialize", which is the standard signal for a client to reconnect and retry (an account holds up to eight sessions at once; opening a ninth lets the longest-idle one go), so a chat you left open overnight picks up where it was rather than dying on the first tool call.

Only known clients can sign in. The sign-in only ever hands its authorization back to an approved MCP client (Claude, ChatGPT, Gemini, Glama, Smithery and VS Code on the web) or to a program on your own machine (localhost). That stops a look-alike app from collecting your access. If a different client fails to connect with an error saying it (or its redirect host) "is not an approved MCP client", it isn't on the list yet: contact 3dCMS to have it added.

The local server (for the generation tools)

To use the paid generation tools, run the server yourself. You'll need Node 18+ and the mcp-server/ folder from the 3dCMS project on your machine, plus an API token. There's nothing to install globally: Claude runs the server directly.

Claude Code

One command (swap in your token and the real path to mcp-server/index.js):

claude mcp add 3dcms \
  -e THREEDCMS_API_TOKEN=tdcms_your_token_here \
  -e THREEDCMS_BASE_URL=https://3dcms.info \
  -- node /path/to/3dCMS/mcp-server/index.js

Claude Desktop

Open Settings ▸ Developer ▸ Edit Config and add a 3dcms entry (forward slashes work fine on Windows):

{
  "mcpServers": {
    "3dcms": {
      "command": "node",
      "args": ["F:/3dCMS-Claude/mcp-server/index.js"],
      "env": {
        "THREEDCMS_API_TOKEN": "tdcms_your_token_here",
        "THREEDCMS_BASE_URL": "https://3dcms.info"
      }
    }
  }
}

Restart Claude Desktop, and the 3dcms tools should appear.

The environment variables

Variable	Required?	Purpose
`THREEDCMS_API_TOKEN`	Yes	Your `tdcms_…` token from the Account page.
`THREEDCMS_BASE_URL`	No	Defaults to `https://3dcms.info`. Point it at a local dev server if you run one.
`THREEDCMS_FAL_KEY`	No	A fal.ai key. Only if set are the paid generation tools available.

Tools not showing up? Local server: check that you're on Node 18+, that the path to index.js is correct and absolute, and (for Desktop) that you restarted the app. A "Not authorized" error means the token is missing, wrong, or was regenerated. Make a fresh one. Hosted connector: make sure the URL is exactly https://3dcms.info/mcp with no trailing path, and that you finished the Google sign-in in the browser tab it opened. Closing that tab early leaves the connector unauthorized.

‹ PreviousGenerate your API token Next ›Connect ChatGPT to 3dCMS

Spotted something off, or want a topic covered? Tell us, a person reads every message.