GoModelHub 3D MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOMODELHUB_API_KEY | Yes | Your GoModelHub API key (starts with gk- or sk-) | |
| GOMODELHUB_BASE_URL | Yes | Base URL for the GoModelHub API, e.g. https://login.gomodelhub.com | |
| GOMODELHUB_DEFAULT_MODEL | No | Default model code from the Model Marketplace (e.g. hyper3d). Optional if model is passed in each request. |
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 |
|---|---|
| generate_3dA | Submit a 3D generation job to GoModelHub. Supports text/URL (JSON) or local image file (multipart). Returns taskId. |
| get_3d_statusB | Poll 3D task status once. When status=succeeded, download via assetUrl with the same API key. |
| generate_3d_and_waitA | Submit a 3D job (JSON or local image) and poll until succeeded/failed or timeout. |
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 3 tools
The three tools are mostly distinct: get_3d_status only polls, generate_3d submits async, and generate_3d_and_wait submits plus polls. However, generate_3d and generate_3d_and_wait share a similar starting action, which could cause minor confusion despite the names making the difference clear.
All tool names use snake_case with a verb-first pattern: get_3d_status, generate_3d, generate_3d_and_wait. The naming is consistent in style, though generate_3d_and_wait is slightly more compound and less uniform than the other two.
Three tools is a well-scoped set for a 3D generation MCP: one async submit, one sync submit-and-wait, and one status poller. Each tool serves a clear purpose without unnecessary bloat.
The tool surface covers the core 3D generation workflow: submitting a job, polling status, and knowing when to download via assetUrl. It lacks explicit cancellation or result-download tools, but those may be outside the intended scope and are not critical gaps.