Server facts
interactive-mcp
Project
- Author
- ttommyth
- Repository
- github.com/ttommyth/interactive-mcp
- License
- MIT
- Category
- Communication
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 351
- Last commit
- Data as of
Tags
- mcp
- mcp server
- vibe coding
- vibecoding
Overview
For setup decisions and code feedback, interactive-mcp connects an AI assistant to the person working on the same machine. The request_user_input tool presents a question in a pop-up command prompt, can include predefined choices, and returns the response. This supports clarification, configuration choices, and confirmation before code changes. Separately, message_complete_notification delivers an operating-system notification to mark a completed response or task.
Longer exchanges use start_intensive_chat to open a console that remains available across questions. The returned session ID links follow-up prompts sent through ask_intensive_chat, while stop_intensive_chat ends the session and closes the window. The conversation history stays visible during the exchange. Built with Node.js and TypeScript, the server runs locally beside an MCP client and needs operating-system access for prompts and notifications. Client configuration examples cover Claude Desktop, Cursor, and VS Code; configuration options also allow prompt timeouts to be adjusted and selected tools or tool groups to be disabled.
interactive-mcp setup notes
- interactive-mcp records stdio only; confirm a network transport upstream before planning remote access.