Human-In-the-Loop MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HITL_DEBUG | No | Enable debug logging. Set to 1 to enable. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_inputC | Create an input dialog window for the user to enter text, numbers, or other data. This tool opens a GUI dialog box where the user can input information that the LLM needs. Perfect for getting specific details, clarifications, or data from the user. |
| get_user_choiceA | Create a choice dialog window for the user to select from multiple options. This tool opens a GUI dialog box with a list of choices where the user can select one or multiple options. Perfect for getting decisions, preferences, or selections from the user. |
| get_multiline_inputA | Create a multi-line text input dialog for the user to enter longer text content. This tool opens a GUI dialog box with a large text area where the user can input multiple lines of text. Perfect for getting detailed descriptions, code, or long-form content. |
| show_confirmation_dialogA | Show a confirmation dialog with Yes/No buttons. This tool displays a message to the user and asks for confirmation. Perfect for getting approval before proceeding with an action. |
| show_info_messageA | Show an information message to the user. This tool displays an informational message dialog to notify the user about something. The user just needs to click OK to acknowledge the message. |
| health_checkA | Check if the Human-in-the-Loop server is running and GUI is available. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| get_human_loop_prompt | Get prompting guidance for LLMs on when and how to use human-in-the-loop tools. This tool returns comprehensive guidance that helps LLMs understand when to pause and ask for human input, decisions, or feedback during task execution. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a clearly distinct purpose: input types (single-line, multi-line, choice), display (info, confirmation), and health check. No overlap in functionality.
Most tools follow verb_noun pattern (get_*, show_*), but health_check deviates slightly. Overall pattern is clear and predictable.
With 6 tools, the set is well-scoped for human-in-the-loop interactions, covering essential input, output, and status checking without excess.
Covers all core HITL interactions (input, choice, confirmation, info display). Minor gaps like file selection or progress indicators, but sufficient for typical use.