Context3D MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAVE_TO_DESKTOP | No | If set to 'true', generated models will be saved to the desktop. | false |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_modelA | Initiates the 3D model generation process. This tool sends a request to create a 3D model based on the provided prompt and parameters. The response includes a main uuid and subscription_key, which must be saved to continue tracking progress through the check_status tool. When the request is successfully sent, the system returns a 'Submitted' message along with information about the uuid and created jobs. Note that the model generation process may take time. |
| download_modelD | show file to browse |
| check_statusA | Checks the status of the 3D model generation process using the subscription_key received from generate_model. This tool returns the status of all jobs related to the model. When all jobs have a 'Done' status, proceed to the download_model step to download the model. If any jobs are not completed (Generating, Waiting), notify the user to wait and check again later. Status can be: 'Done' (completed), 'Generating' (in progress), or 'Waiting' (queued). |
| read_fileB | Read the contents of a file |
| write_fileB | Write content to a file |
| list_directoryC | List the contents of a directory |
| create_directoryB | Create a new directory |
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 7 tools
The tools are cleanly divided into two domains: 3D model generation (generate_model, check_status, download_model) and file system operations (create_directory, list_directory, read_file, write_file). Each tool has a distinct purpose with no overlap, making selection unambiguous.
All tools follow a consistent verb_noun naming pattern (e.g., generate_model, check_status, list_directory). There are no deviations or mixed conventions, ensuring predictability.
With 7 tools, the count is reasonable for a server that combines 3D model generation and auxiliary file operations. However, the file operations are slightly under-scoped (missing delete, rename), preventing a perfect score.
The 3D generation workflow (generate, check, download) is complete, but the file operations miss common actions like delete or rename. Additionally, the download_model tool's description is vague ('show file to browse'), leaving ambiguity about its exact functionality.