Summary
An approval step the person actually sees, instead of a message they might scroll past.
A confirmation dialog in front of a destructive call turns an agent's plan into a decision somebody made, and the choice dialog bounds the answer to a list you supplied instead of parsing free text out of a reply. Everything renders on the host running the server, so this fits a local setup and not a remote one — which is the question health_check answers before the first dialog is needed.
What it is
A server that opens native GUI dialogs on the machine it runs on and returns what the user entered, in 6 tools.
What you get
- A single-value input dialog carrying a prompt, an input type and a default already filled in
- A choice dialog over a list you supply, with single or multiple selection
- A large text area for a description, a block of code or anything longer than a field
- A Yes/No confirmation that gates an action before it runs
- An acknowledgement dialog for telling the user something without asking anything
- A check reporting whether the server is up and a GUI is actually available to draw on
Requirements
A desktop session on the machine running the server, since the dialogs open there rather than in the client — health_check is what tells you whether one is available. MIT, and no account or key.
Setup effort
One command — uvx hitl-mcp-server