swsd-mcp
Related Servers
Alternatives to swsd-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for ConnectWise PSA (Manage) enabling ticket management, time entry, and read-only lookups of companies, contacts, and configurations with role-based access control and bring-your-own-API-keys support.67 npm6MIT
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server for querying Movidesk tickets through the public Movidesk API.31 npm-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that wraps the TeamDynamix Web API, enabling AI assistants to search tickets, manage assets, query the knowledge base, and look up people in your TDX instance.1-
- AlicenseAqualityBmaintenanceMCP server for the Snipe-IT asset management REST API, enabling read and write operations on assets, licenses, accessories, and more.13Apache 2.0
- AlicenseAqualityCmaintenanceMCP server for managing support tickets on Concrete CMS sites via REST API. Enables listing, reading, replying to tickets, and handling projects, attachments, and moderation.2313 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server for NinjaOne RMM that exposes tools for managing organizations, devices, alerts, ticketing, and automation/scripting via NinjaOne's Public API v2.-
TDQS
Scored across 37 tools
Most tools map to a distinct resource+action, and descriptions explicitly delimit boundaries. However, swsd_update_incident overlaps functionally with its 'safer wrapper' siblings swsd_assign_incident and swsd_update_incident_state, and swsd_create_incident overlaps with swsd_create_service_request (both create incidents), leaving mild residual ambiguity.
Every tool uses the same swsd_ prefix followed by a consistent snake_case verb_noun pattern (list_*, get_*, create_*, update_*, add_*, search_*, describe_*, log_*, upload_*). No style mixing or vague verbs; highly predictable.
37 tools is on the heavy side and above the 25-tool comfort threshold. The broad ITSM domain (incidents, problems, tasks, time tracking, catalog, solutions, users, metadata) justifies many of them, but the surface feels large enough that some consolidation or grouping would help.
Incidents are well covered (list/get/create/update plus comments, tasks, assignment, state), but problems lack update/delete, comments lack delete, and no dedicated tools exist for changes/releases despite being cited as valid object types. Notably, swsd_create_solution and swsd_update_solution are referenced in descriptions yet absent from the tool set, a real gap.