Interactive MCP
Vibe coding should have human in the loop! interactive-mcp: Local, cross-platform MCP server for interact with your AI Agent
A MCP Server implemented in Node.js/TypeScript, facilitating interactive communication between LLMs and users. Note: This server is designed to run locally alongside the MCP client (e.g., Claude Desktop, VS Code), as it needs direct access to the user's operating system to display notifications and command-line prompts.
Want a quick overview? Check out the introductory blog post: Stop Your AI Assistant From Guessing — Introducing interactive-mcp
This server exposes the following tools via the Model Context Protocol (MCP):
5 Reviews
Log in to leave a review.
Letting an agent stop and actually ask me before doing something irreversible is the missing manners most setups lack. The interruption points felt well chosen and quick to answer. I would like to script which actions always require a check.
The agent stops and asks before it does the scary thing. That is the whole feature and it matters. Wired it in, got asked at the right moments, approved or vetoed in a keystroke. Human in the loop, done simply.
Forcing a human checkpoint before consequential actions is exactly the control I keep asking these systems for. The prompts landed before the irreversible steps, not after. I would like an audit trail of what was asked and how I answered, for the times I need to explain a decision later.
The premise that vibe coding should keep a human in the loop is correct, and turning that into an MCP that lets an agent pause and ask is a clean implementation of a real principle. In use it interrupted at the moments that mattered, like an ambiguous requirement or a destructive step, rather than peppering me with trivia. The design question it raises is how to tune the frequency, since too many prompts and people start reflexively approving, which defeats the point. A confidence threshold that only escalates genuine uncertainty would help. As a corrective to fully autonomous runs that quietly go wrong, it is a sensible and well-aimed tool.
An MCP that insists on keeping a human in the loop is a polite way of admitting the agent should not be trusted alone, and I respect the honesty. The prompts arrived at sensible moments and did not nag. A timeout default would stop a forgotten question blocking a run.