Skip to main content
Glama
JimCline

hy3d-mcp

by JimCline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hy3d-mcp

No user-submitted related servers found.

    Related Servers

    • Shape Studio MCP Server

      senacula
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to turn a single image into a textured 3D mesh (GLB, OBJ with vertex colours, plus a turntable PNG) entirely on local hardware. Exposes capability reporting, dry-run planning, job queuing, and status/result retrieval so quality presets, hardware tiers, and consented model downloads can be driven through natural language.
      Apache 2.0

    • tripo-mcp-cn

      qianzhi1212
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to generate 3D models through natural language, including text-to-3D and image-to-3D, with tools for checking balance, refining models, converting formats, and a local 3D viewer that works without external network access.
      2
      MIT

    • openfigura-mcp

      reynold-hu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run a fully local 3D asset production pipeline: submit a reference image and a plain-language brief, generate a textured GLB, render multi-view images, inspect results against the renders, and export Blender-checkable scenes through self-describing figure_* tools. Every run also writes a provenance ledger recording inputs, commands, backend versions and output hashes so any artifact can be reproduced or audited.
      1
      AGPL 3.0

    • modelgen

      Guilospanck
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, edit, and export 3D models (GLB, USDZ) from natural-language descriptions and YAML, with rendering and problem detection.
      8 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool addresses a distinct stage: concept preparation, model generation, texturing/finishing, preview rendering, and server diagnostics. There is no functional overlap or ambiguity between them.

    Naming Consistency4/5

    Four of five tools follow a clear verb_noun pattern (prepare_concept, generate_model, finish_model, render_preview). server_status breaks the pattern slightly but remains readable and predictable within the set.

    Tool Count5/5

    Five tools are well-scoped for the server's purpose, covering the essential pipeline without redundancy or bloat. Each tool has a clear role and earns its place.

    Completeness5/5

    The full lifecycle from concept image to finished model preview is covered: prepare concept, generate model, optionally finish texturing, and render preview. server_status adds operational coverage. No critical gaps are apparent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources