the-real-snipeit-mcp
Related Servers
Alternatives to the-real-snipeit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for the Snipe-IT asset management REST API, enabling read and write operations on assets, licenses, accessories, and more.13Apache 2.0
- AlicenseBqualityDmaintenanceRead-only MCP server for Snipe-IT v7 REST API, providing search and retrieval of assets, users, models, categories, and locations without modification.16MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to manage Snipe-IT assets with full CRUD, checkout/checkin, audit, restore, and lookup operations across all supported resource types.11AGPL 3.0
- AlicenseBqualityDmaintenanceMCP 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.20MIT
- AlicenseNot gradedqualityBmaintenanceMCP server providing token-efficient access to OpenAPI/Swagger specs via MCP Resources for client-side exploration.582 npm76MIT
- AlicenseAqualityBmaintenanceMCP 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.521,760 npm5MIT
TDQS
Scored across 183 tools
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.
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.
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.
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.