Summary
Ambiguity gets resolved during the run instead of discovered after it.
Three of the five tools are one shape — open a session, ask into it, close it — which is what makes a requirements conversation practical: the console window opens once rather than once per question. The other two cover the single question and the finished-work ping. Because the prompt renders on the machine the server runs on, this belongs to a local agent loop; a remote client will not see the window.
What it is
A five-tool channel back to the person at the machine: a pop-up prompt, a completion notification, and a reusable console session for a run of questions.
What you get
- A blocking question put to the user in a pop-up prompt, with predefined options when the answer should be a choice rather than free text
- A completion notification at the end of a message, so a long run does not have to be watched
- An intensive chat session — opened once, asked into repeatedly, then closed — for a sequence of related answers instead of a pop-up per question
- A projectName on the prompt and notification calls, so it is clear which session is asking
Requirements
A desktop session on the machine running the server: the prompts and the intensive-chat window open locally, not inside the client. MIT licensed.
Setup effort
One command — npx -y interactive-mcp