Base44
Build and edit Base44 apps from an AI assistant, and query data your app's users submit.
Official MCP demo server rendering interactive WebGL scenes in the chat.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Three.js 3D Viewer is the Model Context Protocol project's own demo server for MCP Apps. Its two tools let an agent write JavaScript against a real WebGL canvas rendered inside the conversation, so a rotating cube or an orbit-controlled model appears as an interactive widget. It is a reference implementation, not a vendor product.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Render an interactive 3D scene with custom Three.js code. Supports transparent backgrounds (alpha: true) for seamless host UI integration. Available globals: THREE, OrbitControls, EffectComposer, RenderPass, UnrealBloomPass, canvas, width, height.
Get documentation and examples for using the Three.js View
Read from the server on 2026-08-18, including each tool's own safety annotations.
ext-apps issue tracker, which serves all twenty-six examples in the repository.code parameter and fetching it from within the widget.success boolean and no picture.works_with as ["claude"].readOnlyHint or destructiveHint, so an agent policy keyed on annotations has nothing to read.No. It is a reference implementation the Model Context Protocol project publishes to demonstrate MCP Apps, hosted at example-server.modelcontextprotocol.io and shipped as one of twenty-six examples in the ext-apps repository. It carries no availability commitment, no service level and no support channel beyond the repository issue tracker. Treat it as a demonstration you can read, run locally and learn from.
No. We opened an anonymous handshake against the endpoint on 2026-08-18 and the server returned both tool definitions, its capability block and its resource listing without any credential. That contradicts the directory entry, which records is_authless as false and an auth posture of auth_required. The wire behaviour is what a client actually meets, so no sign-in is needed.
The listing is empty and the server is not. Anthropic's directory records tool_names as an empty array, while a live tools/list on 2026-08-18 returned two tools, show_threejs_scene and learn_threejs. This is a total absence rather than a partial mismatch, so nothing in the listing describes the surface. Read the tool names from the handshake, never from the directory entry.
In your own MCP client, not on the server. The server declares a resources capability and serves one HTML widget at ui://threejs/mcp-app.html with MIME type text/html;profile=mcp-app, the MCP Apps marker. The show_threejs_scene tool points at that same URI, so a supporting client loads the widget and executes your JavaScript against a WebGL canvas locally.
A documentation string, not a live lookup. The server source shows learn_threejs takes no parameters and returns a fixed Three.js reference bundled into the server: the list of available globals, template scenes for transparent and solid backgrounds, a rotating cube example, an interactive OrbitControls example, and tips on materials, lighting and animation. It never queries the network.
Both tools ship without safety annotations, so the server asserts nothing either way. Neither carries readOnlyHint nor destructiveHint — the fields are absent, not set false. In practice show_threejs_scene runs your JavaScript inside the client widget and learn_threejs returns a static string, but that reading comes from the published source rather than from a declaration on the wire.
The directory lists Claude only, and the widget needs MCP Apps support. Anthropic records works_with as claude alone, so nothing else is listed as compatible. Any MCP client can complete the handshake and call both tools, but a client that does not implement the MCP Apps extension gets text back instead of a rendered scene, which removes the point of the server.
It is a wrong link in the listing. Anthropic's directory publishes the documentation URL as the pdf-server README inside the ext-apps repository, which documents a different example entirely. The correct file is the threejs-server README in the same repository. We confirmed both URLs return 200 on 2026-08-18, so the bad link resolves cleanly to the wrong server's documentation.
modelcontextprotocol/ext-apps — https://github.com/modelcontextprotocol/ext-apps/blob/main/examples/threejs-server/README.md (fetched 2026-08-18, HTTP 200) · retrieved 2026-08-18server.ts — https://github.com/modelcontextprotocol/ext-apps/blob/main/examples/threejs-server/server.ts (fetched 2026-08-18, HTTP 200) · retrieved 2026-08-18initialize, tools/list, resources/list, resources/templates/list and prompts/list handshake against the endpoint — 2026-08-18 · retrieved 2026-08-18modelcontextprotocol.io/ redirects here) · retrieved 2026-07-28Connect Three.js 3D Viewer once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.