Skip to main content
Glama
Disane87

spoolman-mcp

by Disane87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to spoolman-mcp

No user-submitted related servers found.

    Related Servers

    • PrintVaultMCP

      BrandonDoster
      A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to manage 3D printing inventory, filament spools, printers, projects, and print trackers through a self-hosted Print Vault instance.
      40
      AGPL 3.0

    • StashDog MCP Server

      dogfoodlab-io
      F
      license
      B
      quality
      F
      maintenance
      Enables AI assistants to manage StashDog inventory through natural language commands, supporting item management, collections, tags, smart search, and URL imports with secure authentication.
      11
      -

    • Snipe-IT MCP Server

      Wil-Collier
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Snipe-IT inventory systems through comprehensive asset and consumable operations. Supports creating, updating, tracking, and managing IT assets, consumables, maintenance records, file attachments, and generating labels.
      1
      -

    • odin-print-farm-mcp

      HughKantsime
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to operate a 3D print farm via O.D.I.N. backend, including job queuing, printer control, inventory management, and standalone cost calculators.
      6 npm
      Apache 2.0
    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.4/5.0

    Scored across 34 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes (e.g., list_filaments vs list_materials vs list_article_numbers). Some potential confusion exists between use_spool and measure_spool, or get_info and health_check, but descriptions clarify these differences.

    Naming Consistency4/5

    Tools generally follow the spoolman_<verb>_<noun> pattern (e.g., list_vendors, create_filament). Minor deviations like health_check (object before verb) and trigger_backup are present but not disruptive.

    Tool Count2/5

    With 34 tools, the server is well above the typical 3-15 range for coherence. While the breadth covers many Spoolman features, the large number makes it heavy and more complex for agents to navigate.

    Completeness3/5

    Full CRUD exists for vendors, filaments, and spools, plus exports and settings. However, locations only have list and rename—missing create, delete, and get-by-id—which is a notable gap for that entity.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources