Skip to main content
Glama
subhashdasyam

BambuStudio-MCP

by subhashdasyam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to BambuStudio-MCP

No user-submitted related servers found.

    Related Servers

    • Bambu Project QA MCP

      gauravsoodtech
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for pre-print QA of Bambu Studio projects, providing tools to inspect models and 3MF files, validate risky settings, create support variants, and open files in Bambu Studio.
      MIT

    • orcaslicer-mcp

      MaxEllis
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets Claude drive a real, running OrcaSlicer: load models, arrange the plate, tune settings, slice, and read results back.
      53
      419 PyPI
      81
      AGPL 3.0

    • bambu-printer-mcp

      rowbotik
      A
      license
      B
      quality
      C
      maintenance
      A Bambu Lab-focused MCP server for controlling Bambu printers, manipulating STL files, and managing end-to-end 3MF print workflows from any MCP-compatible client.
      37
      29 npm
      GPL 2.0

    • bambu-printer-mcp

      DMontgomery40
      A
      license
      B
      quality
      A
      maintenance
      An MCP server for controlling Bambu Lab 3D printers that enables users to manipulate STL files, slice 3MF files, and manage end-to-end print workflows directly from Claude. It provides real-time status monitoring, file management via FTPS, and printer control through MQTT for a focused, lean Bambu-only implementation.
      46
      98 npm
      242
      GPL 2.0

    • orca-slicer-mcp

      dmikushin
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that drives OrcaSlicer headlessly on a virtual display, enabling an agent to import 3D models, slice them, and export G-code without a physical screen or GUI automation.
      12
      4
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions (projects, settings, geometry, slicing jobs, exports). A few read-oriented tools (inspect_project, inspect_slice, get_settings, list_options) touch adjacent surfaces and could occasionally be confused, but descriptions differentiate scope and intent well.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern (get_settings, apply_settings, start_slice, cancel_job, compare_candidates, export_project). Verb reuse (get_*, inspect_*, open_*) is applied meaningfully to different objects rather than chaotically.

    Tool Count4/5

    19 tools is on the heavier side but the domain (project editing, config, geometry analysis, slicing, job management, comparison, export) is genuinely broad. Each tool maps to a distinct operation and none appears redundant or filler.

    Completeness4/5

    The surface covers a full design-to-export lifecycle: open/import, inspect, read and apply settings, edit regions, analyze geometry, slice, poll/cancel jobs, compare candidates, restore revisions, and export. Minor gaps like listing/managing existing projects or deleting revisions are workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources