3d-texture-toolkit-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_pbr_mapsA | Extract embedded base color and normal images, and split the glTF metallic-roughness image into roughness and metallic PNG files. Reads and writes local files only. |
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 1 tool
With only one tool, there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its purpose is clearly scoped to extracting PBR maps.
The single tool name follows a clear verb_noun snake_case pattern: extract_pbr_maps. Although consistency across a larger set cannot be assessed, the available name is predictable and readable.
A single tool is borderline thin for a server named as a texture toolkit. It may be adequate for narrow PBR extraction, but the name implies broader texture-processing capability.
The surface covers extraction and channel splitting of existing PBR maps, but lacks complementary operations such as packing maps, validating inputs, or handling other texture workflows. For a toolkit, this leaves significant gaps.