Three.js 3D Viewer
Render interactive 3D scenes and models
About Three.js 3D Viewer
Three.js 3D Viewer is an official MCP Apps example for rich interactive output. Its hosted remote MCP server generates browser-rendered 3D scenes, models, and animations inside a conversation, demonstrating visual tools built with Three.js.
Connection details
https://example-server.modelcontextprotocol.io/threejs/mcp- Transport
- Streamable HTTP
- Authentication
- OAuth
Setup
claude mcp add three-js-3d-viewer --transport http https://example-server.modelcontextprotocol.io/threejs/mcpFrequently asked questions
What is the Three.js 3D Viewer remote MCP server?
The Three.js 3D Viewer remote MCP server is a hosted Model Context Protocol endpoint at https://example-server.modelcontextprotocol.io/threejs/mcp, so AI assistants can connect to it without installing or running anything locally. Three.js 3D Viewer is an official MCP Apps example for rich interactive output. Its hosted remote MCP server generates browser-rendered 3D scenes, models, and animations inside a conversation, demonstrating visual tools built with Three.js.
How do I connect to the Three.js 3D Viewer MCP server?
Add the endpoint https://example-server.modelcontextprotocol.io/threejs/mcp to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the Three.js 3D Viewer MCP server require authentication?
Yes. Three.js 3D Viewer uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Which transport does the Three.js 3D Viewer MCP server use?
Three.js 3D Viewer exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.
