Skip to main content
Glama
AaronGoldsmith

mcp-printable

by AaronGoldsmith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-printable

No user-submitted related servers found.

    Related Servers

    • Blender Open MCP

      Ramos03367
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect and control a live Blender session through MCP tools that create, modify, and delete objects, apply materials, render images, execute Python, and pull PolyHaven assets over a local TCP add-on. It also exposes a provider-agnostic LLM layer that can be pointed at Ollama, LM Studio, llama.cpp, OpenAI-compatible, or Azure endpoints and switched at runtime.
      -

    • 3d-printagent

      huy97
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage multiple 3D printers via MCP, including monitoring temperatures and progress, uploading and slicing models, controlling prints, and viewing cameras.
      7 npm
      MIT

    • openscad-mcp

      jkoets
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to create and manipulate 3D models using OpenSCAD through MCP tools for code-based modeling, preview, and export.
      1
      MIT

    • Blender Open MCP

      YuqiMeyer4302
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a live Blender session over MCP — inspecting and creating scene objects, applying materials, rendering, executing code, and fetching PolyHaven assets. It also exposes prompt, provider, and model tools backed by a provider-agnostic LLM layer (Ollama, LM Studio, llama.cpp, OpenAI-compatible, Azure) that can be switched at runtime.
      -
    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

    A3.9/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target distinct operations, but rendering tools (screenshot vs tiled vs turntable) and cross-section tools (single vs gallery) have overlapping purposes that could confuse agents. The descriptions mitigate ambiguity but don't fully eliminate it.

    Naming Consistency5/5

    All tools follow a consistent pattern: engine prefix (blender_/scad_) + verb + noun(s), all lowercase with underscores. Verbs vary (import, get, clear, render, check, validate, export, etc.) but the naming style is uniform and predictable.

    Tool Count2/5

    With 29 tools, the set exceeds the 25+ threshold for 'too many.' While the two-engine scope (Blender and OpenSCAD) partially justifies the count, the sheer number is heavy and risks overwhelming agents.

    Completeness5/5

    The toolset covers the full 3D-printing workflow: import, geometry creation/editing (via execute_code and boolean), inspection (renders, cross-sections), printability validation (overhang, thin walls, clearance, intersection, retention), and export (STL, BLEND, SCAD). No critical gaps are apparent.

    Maintenance

    ActivityInactive
    ResponsivenessSlow

    Resources