Skip to main content
Glama
the-real-snipeit-mcp

the-real-snipeit-mcp

Related Servers

Alternatives to the-real-snipeit-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for the Snipe-IT asset management REST API, enabling read and write operations on assets, licenses, accessories, and more.
      13
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Read-only MCP server for Snipe-IT v7 REST API, providing search and retrieval of assets, users, models, categories, and locations without modification.
      16
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to manage Snipe-IT assets with full CRUD, checkout/checkin, audit, restore, and lookup operations across all supported resource types.
      11
      AGPL 3.0
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for JumpCloud APIs with full OpenAPI-driven coverage, enabling endpoint discovery, operation invocation, and direct API requests while managing multi-tenant user tokens in Vault and guarding mutating tools.
      20
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing token-efficient access to OpenAPI/Swagger specs via MCP Resources for client-side exploration.
      582 npm
      76
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for SolarWinds Service Desk (SWSD/Samanage) enabling reading and modifying tickets, comments, knowledge-base articles, and more via each user's own API token.
      52
      1,760 npm
      5
      MIT

    TDQS

    D1.9/5.0

    Scored across 183 tools

    Disambiguation1/5

    The surface is dominated by duplicate coverage of the same endpoints: list_hardware vs gen_hardware_list, create_hardware vs gen_hardware_create, checkout_hardware vs gen_hardware_checkout, plus raw_request as a universal escape hatch. Agents cannot reliably choose between semantic tools and generated tools, and many gen_* names differ only by opaque suffixes.

    Naming Consistency2/5

    There are two competing naming schemes: readable semantic names like snipeit_list_hardware and generated names like snipeit_gen_hardware_list and snipeit_gen_fieldsid_3. The generated names use inconsistent numeric suffixes and tangled operation names, making verb/noun intent unpredictable despite staying in snake_case.

    Tool Count1/5

    183 tools is far beyond a reasonable scoped surface for this server, especially because many tools are near-duplicates of the same endpoint. The count creates overwhelming selection noise rather than adding useful capability.

    Completeness2/5

    Broad Snipe-IT resources are represented, but the surface has severe redundancy, broken/incomplete tools such as file uploads that explicitly do not work, and odd generated endpoints. Coverage is technically wide but operationally unreliable and hard to navigate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues