Cursor, VS Code, Claude Code, Codex, Gemini CLI, Antigravity and other MCP clients

3dCMS is a remote MCP server at https://3dcms.info/mcp, using streamable HTTP with OAuth (you sign in with Google in your browser). Any client that supports both can connect with one entry in its MCP config: a name and that URL. The sign-in only hands its authorization to approved web clients or to a program on your own machine (localhost), which covers the desktop and terminal tools below.

The config keys differ from client to client, and clients change them between versions, so treat these as the shape to look for and check your client's own MCP documentation if one does not take.

Claude Code

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

Then run /mcp inside Claude Code and pick 3dcms to sign in.

Cursor

In ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "3dcms": { "url": "https://3dcms.info/mcp" }
  }
}

Cursor should offer a sign-in for the server in its MCP settings.

VS Code

In .vscode/mcp.json, or through the MCP: Add Server command:

{
  "servers": {
    "3dcms": { "type": "http", "url": "https://3dcms.info/mcp" }
  }
}

Start the server from the file or the command palette and VS Code walks you through the sign-in. VS Code on the web (vscode.dev) is on the approved list too.

Windsurf

In ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "3dcms": { "serverUrl": "https://3dcms.info/mcp" }
  }
}

Codex CLI

In ~/.codex/config.toml, then codex mcp login 3dcms to sign in:

[mcp_servers.3dcms]
url = "https://3dcms.info/mcp"

Gemini CLI and Antigravity CLI

Google is replacing Gemini CLI with Antigravity CLI for free users (since June 18, 2026). Both read the same kind of entry. Using the Gemini app in the browser instead? See Connect Gemini to 3dCMS.

In ~/.gemini/settings.json, then /mcp auth 3dcms inside Gemini CLI to sign in:

{
  "mcpServers": {
    "3dcms": { "httpUrl": "https://3dcms.info/mcp" }
  }
}

Anything else

A client that speaks streamable HTTP and OAuth 2.1 (with dynamic client registration and PKCE, which is what most current clients do) should connect from the URL alone. Before you sign in it can already list the thirteen tools, which is a quick way to check the URL is right; every call is refused until the sign-in finishes. Directories that read the official MCP registry know the server as info.3dcms/mcp.

If the sign-in page answers that your client "is not an approved MCP client", its redirect address is not on the list. Email hello@3dcms.info with the client's name and that address, and it can be added.

The local server alternative

The mcp-server/ folder runs the same tools on your own machine over stdio, signed in with an API token instead of Google. It is the only way to get the paid generation tools (generate_3d and generate_material, listed when a fal.ai key is set in its config). It needs Node 18+; the Claude Code and Claude Desktop entries are in Connect Claude to 3dCMS, and any client that runs stdio servers takes the same command, args and env.