Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Kiln

Related Servers

  • Klipper MCP Server

    Charleslotto
    F
    license
    Not graded
    quality
    B
    maintenance
    An MCP server that enables AI assistants to control and monitor Klipper 3D printers via the Moonraker API. It supports comprehensive printer management, including G-code execution, toolchanger operations, and real-time status monitoring.
    22
    -

  • pycentauri MCP server

    bjan
    A
    license
    Not graded
    quality
    B
    maintenance
    An MCP server that enables AI agents to monitor and control an Elegoo Centauri Carbon 3D printer via local network, supporting status checks, snapshots, and print control.
    22
    Apache 2.0

  • mcp-printable

    AaronGoldsmith
    A
    license
    A
    quality
    B
    maintenance
    Connects MCP-capable agents to Blender and OpenSCAD for AI-driven 3D modeling, with tools and rules optimized for FDM-printable geometry.
    29
    2
    MIT

  • fusion-mcp

    prim-design
    A
    license
    Not graded
    quality
    D
    maintenance
    Open-source MCP server for controlling Autodesk Fusion 360 from any AI agent, enabling 3D modeling operations via natural language.
    2
    MIT

  • mojulo

    zombico
    F
    license
    Not graded
    quality
    A
    maintenance
    A local MCP server that lets coding agents turn conversational prompts into deterministic, re-runnable recipes for 3D objects, walkable worlds, and playable games, all stored on your own disk without API keys or cloud rendering. Those recipes can be edited in place and exported to the browser, Godot, Unity, Unreal, Blender, glTF/OpenUSD, or print-ready STL and 3MF at true scale.
    -
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

B3.1/5.0

Scored across 468 tools

Disambiguation1/5

With 468 tools, the surface is riddled with strings of near-identical tools that do the same thing: get_material_info/get_material_properties/get_material_design_profile (and several more material lookups), plus a range of analyze/diagnose/check print-issue, mesh-analysis, and failure-recovery tools. Even with detailed descriptions, an agent cannot reliably select between them, especially when tools with the same behavior are named differently.

Naming Consistency3/5

Tool names are uniformly snake_case, but no consistent verb-first pattern emerges. Many use noun-first conventions (printer_status, job_status, queue_summary) while others use verb_* (list, get, check, validate, analyze, monitor, watch, run), and there are contradictory subtleties such as multiple merge commands (merge_stl, merge_mesh_files, compose_models, merge_multicolor_gcode). There is no mixed casing or random names, but the vocabulary is broad and overlapping.

Tool Count1/5

468 tools is far beyond the 3-15 well-scoped range; even for a comprehensive 3D-printing server, this is extreme over-provisioning. Such a large count inflates the model's context, yields massive overlaps, and makes the set far more difficult to navigate than a compact, curated tool set.

Completeness4/5

The surface is incredibly broad: full print lifecycle, slicing, mesh analysis, generation, material management, fleet, marketplaces, fulfillment, cost, recovery, security, enterprise, and team tools. There are minor gaps (e.g., no printer deletion/rename, no generic update for shipping profiles, and some deprecated aliases are honored) but almost every domain has a viable workflow path from start to finish.

Maintenance

ActivityActive
ResponsivenessSlow

Resources