A
licenseB
qualityA
maintenanceEnables interaction with 3D printer management systems through an MCP server, supporting STL file manipulation, slicing, and control of printers like OctoPrint, Klipper, Duet, and more.
30
119 npm
256
GPL 2.0
Kiln
by codeofaxel
Related Servers
Alternatives to Kiln
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows AI assistants to search for, explore, and retrieve 3D printable models from Thingiverse.7MIT
- AlicenseNot gradedqualityFmaintenance3D Printing MCP By OctoEverywhere38Apache 2.0
Related Servers
- FlicenseNot gradedqualityBmaintenanceAn 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.27-
- AlicenseNot gradedqualityCmaintenanceMCP server for generating print-ready 3D models from text descriptions via a multi-agent pipeline, enabling AI assistants to create and optimize STL files.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage multiple 3D printers via MCP, including monitoring temperatures and progress, uploading and slicing models, controlling prints, and viewing cameras.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn 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.23Apache 2.0
- AlicenseAqualityDmaintenanceConnects MCP-capable agents to Blender and OpenSCAD for AI-driven 3D modeling, with tools and rules optimized for FDM-printable geometry.2955 PyPI2MIT
- AlicenseNot gradedqualityDmaintenanceOpen-source MCP server for controlling Autodesk Fusion 360 from any AI agent, enabling 3D modeling operations via natural language.3MIT
TDQS
C2.6/5.0
Scored across 851 tools
Disambiguation1/5
Dozens of tools have near-identical purposes: slice_and_estimate, estimate_print_time, estimate_material_cost, estimate_print_cost_from_mesh, estimate_cost, estimate_mesh_weight and estimate_mesh_print_time all answer 'time/filament/cost'; validate_and_prepare, validate_and_prepare_mesh, validate_generated_mesh, check_print_readiness and audit_original_design all gate the same mesh; merge_stl, merge_mesh_files and compose_models concatenate meshes; visualize_model, render_model_preview, preview_generated_model, inspect_mesh_view and show_on_stage all render images. Several deprecated aliases (print_status_lite, repair_mesh_advanced, render_model_preview, recover_texture_detail) sit beside their replacements with no removal. An agent cannot reliably pick among these without reading long prose.
Naming Consistency3/5
The dominant pattern is snake_case verb_noun (list_designs, create_design_branch, retire_feature_release), which is readable and mostly predictable. But conventions are mixed: namespace prefixes that invert the order (fleet_status, cloud_remote_list, kiln_health), noun-first names (may_i_print, axis_report style), and product generators all named generate_<object> alongside generate_model, generate_from_template, generate_model_with_provider, generate_and_print. Deprecated duplicates with no naming distinction compound the inconsistency.
Tool Count1/5
851 tools is an extreme mismatch for any single MCP surface; the descriptions alone exceed a context window, so an agent cannot survey the set before choosing. Large blocks are tier-gated stubs (Business/Enterprise) that cannot even run on the installing tier, and many are verbatim duplicates or deprecated aliases rather than earned capabilities.
Completeness4/5
The domain — an end-to-end 3D printing workspace (design, version, cloud sync, slice, print, monitor, repair, marketplace, fulfillment, fleet, org/teams) — is covered to an unusual depth, with CRUD, lifecycle, branching, releases and audit all present. Gaps are minor and mostly integration-specific (e.g. Klipper power-loss recovery noted as unsupported), not surface-level.
Maintenance
ActivityActive
ResponsivenessSlow