Skip to main content
Glama
borgels

mcp-server-snipe-it

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-server-snipe-it

No user-submitted related servers found.

    Related Servers

    • snipeit-mcp

      chiku-wa
      A
      license
      B
      quality
      B
      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

    • snipe-it-mcpprivate

      wyre-technology
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Snipe-IT asset management, enabling users to read and manage IT assets, models, manufacturers, and related data through natural language. Designed to feed inventory into lifecycle audits.
      Apache 2.0

    • swsd-mcp

      mikimatsub
      A
      license
      A
      quality
      A
      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.
      37
      40 npm
      3
      MIT

    • GLPI MCP Server v2

      Luizcc87
      A
      license
      C
      quality
      A
      maintenance
      MCP server for GLPI integration, providing tools for ITIL management (tickets, problems, changes, knowledge base, stats, assets, and administration) via the GLPI API.
      30
      MIT

    • SuperOps MCP Server

      Matt-Beyond-Tech
      A
      license
      A
      quality
      C
      maintenance
      MCP server for interacting with the SuperOps.ai PSA/RMM platform, providing tools for managing clients, tickets, assets, and technicians via GraphQL API.
      21
      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

    A3.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a distinct purpose: audit, checkin, checkout, CRUD for assets vs other entities, and reporting. No overlapping functionality.

    Naming Consistency4/5

    All tools start with 'snipeit_' followed by a verb_noun pattern (e.g., create_asset, list_entities), but 'checkin' and 'checkout' deviate slightly as single verbs, and 'search_capabilities' is less standard.

    Tool Count5/5

    13 tools cover the essential operations for an asset management system: CRUD, checkin/checkout, audit, and search. The count feels well-scoped without being excessive.

    Completeness3/5

    Covers core create, read, update, checkin/checkout, and audit, but lacks delete operations for both assets and other entities, which is a notable gap in lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources