Skip to main content
Glama
LauOtero

Klipper MCP Server

by LauOtero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Klipper MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-cli-catalog

      abcpro1
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that publishes CLI tools on your machine for discoverability by LLMs
      7 npm
      1
      MIT

    • github-mcp

      awernick
      F
      license
      A
      quality
      D
      maintenance
      MCP server exposing GitHub tools for issues, pull requests, and code browsing via the GitHub REST API. Designed for local LLM clients with flat arguments and streamable HTTP support.
      15
      -

    • home-assistant-mcp

      Vortitron
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP-speaking coding agents to talk directly to Home Assistant and the ESPHome dashboard: discovering entities and areas, reading live states, history and logs, rendering Jinja templates, calling services, and creating, editing or triggering automations and dashboards. Also allows ESPHome device configs to be read, validated, compiled and flashed, with all write operations off by default behind an explicit safety policy.
      111
      73 npm
      MIT
    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

    C2.7/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (config files, validation, server info, runtime status, logs, G-code execution). However, verify_component_loaded vs verify_extra_loaded and get_printer_status vs list_objects/get_print_progress have somewhat overlapping scopes that could cause occasional misselection.

    Naming Consistency5/5

    Tool names consistently use snake_case with a predictable verb_noun pattern (get_*, list_*, verify_*, validate_*, run_*). There is no mixed casing or vague naming, making the set easy to scan.

    Tool Count4/5

    17 tools is slightly above the ideal range but reasonable for a server covering Klipper config validation, Moonraker diagnostics, telemetry, and printer control. Each tool appears to have a distinct purpose, though the surface is on the heavier side.

    Completeness3/5

    The server covers reading, listing, searching, validating configs, plus diagnostics, logs, and basic control. However, it lacks config write/update/delete operations and print lifecycle controls like pause/resume/cancel, leaving some common Klipper management workflows incomplete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources