hitl-mcp-server
Related Servers
Alternatives to hitl-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables conversational triage of ServiceNow incidents via Claude Desktop, automatically classifying and routing them based on company knowledge.-
- FlicenseNot gradedqualityDmaintenanceConnects Claude Desktop directly to a ServiceNow instance for incident management, service catalog, workflow tools, and AI-powered smart incidents and KB generation using Gemini.-
- AlicenseCqualityCmaintenanceEnables Claude Desktop to autonomously perform HR operations such as employee onboarding, leave management, meeting scheduling, ticket creation, and email notifications through MCP tool calling.12MIT
- FlicenseBqualityCmaintenanceEnables Claude Desktop to autonomously handle HR workflows through natural language, including employee onboarding, leave management, meeting scheduling, and IT/admin ticketing.8-
- FlicenseNot gradedqualityCmaintenanceConnects Claude Desktop to the IT Asset Tracker backend, enabling natural language management of assets, users, requests, and reports via 70+ auto-generated tools.-
- FlicenseNot gradedqualityCmaintenanceExposes a ticket classification tool that categorizes support tickets by severity, category, sentiment, and summary via MCP, using the Anthropic API for classification and packaged as a Claude Desktop extension.-
TDQS
Scored across 6 tools
Each tool targets a distinct action on HITL escalations—create, approve, modify, reject, get, list—with no overlapping purposes. An agent can easily select the right tool based on the desired operation.
All tools follow a consistent verb_hitl pattern (e.g., create_hitl, approve_hitl, list_hitls), using snake_case throughout. The pluralization in list_hitls is a minor deviation but still follows the expected convention.
With 6 tools, the server is well-scoped for managing HITL escalations. Each tool covers a necessary action without redundancy, fitting comfortably within the ideal range.
The toolset covers the full lifecycle of a HITL escalation: creation (create_hitl), retrieval (get_hitl, list_hitls), updates (modify_hitl), and state transitions (approve_hitl, reject_hitl). No obvious gaps for the intended domain.