MCP Three
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-model-structureA | Get the structure of a GLTF/GLB model file. This tool loads the file and returns the parsed scene structure as JSON, using GLTFStructureLoader from gltfjsx. Use this tool for complex model debugging and not implementation. For code generation use the gltfx tool. |
| gltfjsxA | Converts a GLTF/GLB 3D model file into a reusable, declarative React (react-three-fiber) JSX component. Supports options for TypeScript output, mesh/material instancing, pruning, compression, texture format, mesh simplification, and more. Useful for integrating 3D assets into React apps with optimal performance and flexibility. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get-model-structure is for debugging and analysis by returning parsed JSON structure, while gltfjsx is for code generation by converting models into React components. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.
The tool names follow different conventions: get-model-structure uses kebab-case with a verb-noun pattern, while gltfjsx is a specific tool name without a clear verb. This minor deviation prevents a perfect score, but the names are still readable and descriptive enough for their functions.
With only 2 tools, the server feels thin for handling GLTF/GLB models, as it might lack operations like model validation, editing, or export. However, the tools cover core tasks of analysis and code generation, making it borderline appropriate but potentially incomplete for broader workflows.
The server covers two key aspects: model structure analysis and React component generation. However, there are notable gaps, such as no tools for model creation, updating, or deletion, and no support for non-React frameworks or basic file operations, which could limit agent capabilities in full model lifecycle management.