Skip to main content
Glama
chiku-wa

snipeit-mcp

by chiku-wa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to snipeit-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-server-snipe-it

      borgels
      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

    • 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

    • action1-mcp

      molnkontakt
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for the Action1 RMM REST API, enabling access to endpoints, missing updates, vulnerabilities, installed software, policies, automations, and reports.
      21
      Apache 2.0

    • invgate-mcp

      wdelcant
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for InvGate Asset Management, enabling natural language queries for assets, people, computers, servers, software, and API health.
      12
      6 npm
      1
      MIT
    • KVMFleet MCP Server by KVMFleet

      KVMFleet MCP Serverofficial

      KVMFleet
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server that allows AI assistants to query and monitor KVM Fleet devices, audit logs, and console sessions through the official REST API.
      5
      5 npm
      1
      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

    B3.2/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools map to a distinct resource and action, like get_asset, list_assets, create_asset. The only close pair is assign_license_seat_to_asset and assign_specific_license_seat_to_asset, but their descriptions clearly differentiate auto-selection vs. explicit seat ID.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (get, list, create, check, assign, unassign). Even compound targets like list_license_seats and assign_license_seat_to_asset fit the pattern cleanly.

    Tool Count4/5

    At 16 tools, the set is slightly above the ideal 3-15 range, but the scope justifies it: assets, licenses, users, and reference data (categories, locations, models) are all covered. No bloat or redundant tools beyond the closely related seat assignment pair.

    Completeness3/5

    Core asset and license workflows are covered (create, get, list, license seating), but major gaps exist: no update_asset, delete_asset, asset checkin/checkout, or license update/delete. User management is limited to read-only, and reference data cannot be modified.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources