Skip to main content
Glama
GoModelHub 3D MCP

GoModelHub 3D MCP

Official
by gomodelhub

GoModelHub 3D MCP

MCP server for the GoModelHub 3D generation API — use it in Cursor and other AI Agents with natural language.

English · 中文文檔 · 日本語 · Deutsch · Report Bug · Deploy Guide


Features

  • Zero-config Remote MCP — Streamable HTTP, no local install needed

  • Local stdio MCP — supports local imagePath for image-to-3D

  • 3 Tools — generate_3d, get_3d_status, generate_3d_and_wait

  • Cross-platform — Windows / macOS / Linux

Related MCP server: Meshy MCP Server

Tools

Tool

Description

generate_3d

Submit a 3D job; returns taskId

get_3d_status

Poll task status

generate_3d_and_wait

Submit and poll until done (recommended)

Prerequisites

  • Node.js 18+

  • Platform API Key (gk- / sk-) — get it from GoModelHub

  • modelCode from Model Marketplace (e.g. hyper3d)


Default Model

Mode

Where

Example

Remote MCP

headers

"X-GoModelHub-Default-Model": "hyper3d"

Local MCP

env

"GOMODELHUB_DEFAULT_MODEL": "hyper3d"

Use the modelCode shown in Model Marketplace (no tp- prefix).


Remote MCP does not support local imagePath. Use a public image URL for image-to-3D.

{
  "mcpServers": {
    "gomodelhub-3d": {
      "url": "https://login.gomodelhub.com/mcp/3d",
      "headers": {
        "Authorization": "Bearer gk-your-key",
        "X-GoModelHub-Default-Model": "hyper3d"
      }
    }
  }
}

See examples/mcp.remote.json.


Option 2: Local MCP (supports imagePath)

Install

git clone https://github.com/kelouer/GoModelHub-MCP.git
cd GoModelHub-MCP
npm install
npm install -g .

OS

Command

Windows

powershell -ExecutionPolicy Bypass -File scripts/install-global.ps1

macOS / Linux

bash scripts/install-global.sh

Verify: where gomodelhub-3d-mcp (Windows) or which gomodelhub-3d-mcp.

Configure

{
  "mcpServers": {
    "gomodelhub-3d": {
      "command": "gomodelhub-3d-mcp",
      "env": {
        "GOMODELHUB_BASE_URL": "https://login.gomodelhub.com",
        "GOMODELHUB_API_KEY": "gk-your-key",
        "GOMODELHUB_DEFAULT_MODEL": "hyper3d"
      }
    }
  }
}

See examples/mcp.local.json. Save and Refresh.

Local image-to-3D

{ "model": "v3.1-20260211", "imagePath": "D:/photos/chair.jpg", "mode": "image" }

Supports jpg / png / webp, max 50MB.


Comparison

Remote MCP

Local MCP

Install

None

npm install -g .

Text-to-3D

✅

✅

Public image URL

✅

✅

Local imagePath

❌

✅


Troubleshooting

Symptom

Fix

disconnected

Ensure gomodelhub-3d-mcp is on PATH

Missing GOMODELHUB_BASE_URL

Check env in mcp.json

model is required

Set default model or pass model in the call

HTTP 401 / 403

Invalid key or insufficient quota

Remote image-to-3D fails

Use public image URL or local MCP


License

MIT — see LICENSE.

Available Tools

3 tools
generate_3dA

Submit a 3D generation job to GoModelHub. Supports text/URL (JSON) or local image file (multipart). Returns taskId.

Inputs: mode, image, model, prompt, +2 more.

generate_3d_and_waitA

Submit a 3D job (JSON or local image) and poll until succeeded/failed or timeout.

Inputs: mode, image, model, prompt, +4 more.

get_3d_statusB

Poll 3D task status once. When status=succeeded, download via assetUrl with the same API key.

Inputs: taskId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers