3dCMS

What 3dCMS does

The 3dCMS MCP server is intended for creating 3D websites through a conversational workflow. Instead of describing a conventional page builder, the available information focuses on placing website content in three-dimensional space and producing a published result.

Its stated scope includes three kinds of website content:

• Pages that make up the site
• 3D models placed in the experience
• Text positioned in 3D space

The result can be published to a live URL. This makes the server relevant to projects that need a viewable 3D web experience rather than an artifact that remains only in a local editor or chat session.

How it works

Interaction is chat-based. An agent can be used to describe or build the website, with pages, models, and text serving as the main content elements identified in the available description. The workflow therefore centers on communicating the intended site structure and spatial content through conversation.

The 3dCMS MCP server is best evaluated as a conversational website-building tool for 3D content. The provided material does not explain the underlying rendering system, how spatial placement is expressed, or whether changes can be revised incrementally after publication.

Publishing is part of the described workflow: once the 3D website has been built, it can be made available at a live URL. The source does not specify whether that URL is configurable, how domains are handled, or what deployment controls are available.

Limitations and notes

The available source material is brief. It does not document installation commands, environment variables, authentication, transport options, API credentials, supported MCP clients, or licensing. It also does not list individual MCP tool names or provide examples of requests.

For that reason, confirm the setup process and client compatibility from the project’s own documentation before adopting the 3dCMS MCP server in an automated workflow. The material supports the core use case—building and publishing a 3D website through chat—but does not establish details about hosting, persistence, collaboration, access control, model formats, text styling, or page limits.

Use the server when the required outcome is clearly a chat-built 3D website containing pages, models, and text in space. If the project depends on a particular editor, deployment provider, file format, or MCP client, those requirements cannot be verified from the supplied information.