Skip to main content
Glama

Related Servers

Alternatives to splatmaker-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      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.
      3
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to inspect, convert, and compress 3D Gaussian splat files, extract mesh colliders, and drive cloud radiance-field generation or local RTX training through a stdio MCP interface. It also runs headless benchmark recipes that emit run.json and markdown reports.
      6
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes an MCP endpoint that lets agents build parametric, print-ready 3D models (lettering signs, LED light boxes, organizers and gadgets, and terrain or route maps) by listing generators, inspecting their parameter schemas, and submitting job definitions. Also summarizes finished jobs with sizes, colors, weights and render paths, looks up colors and places/routes, saves image prompts, and slices results with OrcaSlicer to report print-path problems.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding assistants and agents to natively generate images, videos, 3D meshes, Gaussian splats, and speech, and to manage media assets, through natural language commands or automated scripts over the Model Context Protocol. It exposes 55 tools alongside a Python CLI automation suite for batch generation, camera-orbit passes, credit/cost estimation, and companion API bridge integration.
      51
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation3/5

    splat_generate multiplexes five operations (create, status, list, get_asset) while show_status_card and splat_engine_status both report engine/job state, so an agent can plausibly reach for splat_generate(operation='status') or show_status_card for the same information. The descriptions distinguish them somewhat (card vs. raw status), but boundaries are soft.

    Naming Consistency4/5

    All names are snake_case and readable; two share the splat_ prefix while server_shutdown and show_status_card do not, and verbs vary (generate, status, shutdown, show). Minor deviation from a strict verb_noun pattern but nothing confusing.

    Tool Count4/5

    Four tools is a tight surface, but splat_generate absorbs five operations internally, so the effective capability set is reasonable for a focused splat-generation server. Nothing feels padded, though the count is on the low side.

    Completeness3/5

    The pipeline lifecycle is covered end to end: start job, poll status, list jobs, fetch assets, plus engine diagnostics. However there is no cancel/delete job operation and no way to inspect a job's logs or failures, which are meaningful gaps for long-running background jobs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues