swsd-mcp
Related Servers
Alternatives to swsd-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceMCP server for the Freshservice ITSM API v2: tickets, changes, problems, assets, requesters, agents, knowledge base and service catalog.27633 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceMCP 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.116 npm6MIT
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server for querying Movidesk tickets through the public Movidesk API.-
- 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-
- AlicenseAqualityCmaintenanceMCP 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.2349 npmMIT
TDQS
Scored across 52 tools
Most resources (incidents, problems, solutions, users, groups, sites) are cleanly separated, but the incident-listing surface is crowded: swsd_list_incidents, swsd_list_my_incidents, swsd_my_queue, swsd_sla_risk and swsd_ticket_stats all return overlapping incident rows and require careful reading to pick correctly. There is also genuine confusion between swsd_update_task (which takes is_complete) and swsd_update_task_state, and between incident-specific comment tools and the generic record comment tools.
The dominant pattern is a uniform swsd_verb_noun scheme (swsd_get_incident, swsd_list_users, swsd_create_problem, swsd_update_comment), which makes the set predictable. A minority of tools break the verb-first pattern (swsd_sla_risk, swsd_my_queue, swsd_ticket_stats, swsd_change_calendar, swsd_health_check), but they are still readable and consistently prefixed.
52 tools is well beyond a comfortable agent-facing surface for what is essentially one ITSM domain, and many are near-duplicate incident views or thin per-resource getters (get_role, get_site, get_department) that could be collapsed. The size forces the agent to scan a large decision space before every call.
Incidents have strong lifecycle coverage (create/get/update/state/assign/comments/tasks/time/attachments/audits/SLA), but changes and releases only have read-side helpers (comments, tasks, calendar, audits) with no get/create/update tools. swsd_create_solution and swsd_update_solution are referenced inside swsd_describe_custom_fields and swsd_search_solutions yet do not appear in the tool list, and no delete operations exist anywhere.