interactive-mcp
Local MCP server that puts a human in the loop: ask the user questions and send OS notifications mid-task.
Add to your client
Copy the config for your MCP client and paste it into its config file.
npx -y interactive-mcpPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"interactive-mcp": {
"command": "npx",
"args": [
"-y",
"interactive-mcp"
]
}
}
}Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- Node.js (see package.json for version compatibility)
- npx command available on PATH
- An MCP client that runs the server locally (Claude Desktop, Cursor, or VS Code)
About interactive-mcp
interactive-mcp facilitates interactive, human-in-the-loop communication between an LLM and the user on their local machine. It exposes MCP tools to ask the user questions (optionally with predefined options), send OS notifications when work is done, and run a persistent command-line 'intensive chat' session for back-and-forth exchanges. This is useful for interactive setup/configuration, gathering feedback during code generation, clarifying instructions in pair programming, and confirming actions before the AI proceeds. It runs cross-platform (Windows, macOS, Linux) via npx over stdio.
Tools & capabilities (5)
request_user_inputAsks the user a question and returns their answer. Can display predefined options.
message_complete_notificationSends a simple OS notification.
start_intensive_chatInitiates a persistent command-line chat session.
ask_intensive_chatAsks a question within an active intensive chat session.
stop_intensive_chatCloses an active intensive chat session.
When to use it
- Interactive setup or configuration processes driven by an AI assistant
- Gathering user feedback during code generation or modification
- Clarifying instructions or confirming actions in pair programming
- Any workflow requiring user input or confirmation during LLM operation
- Sending an OS notification when a long-running AI task completes
Security notes
Runs locally and requires direct access to the user's operating system to display command-line prompts and OS notifications. By default, user prompts time out after 30 seconds (configurable via the -t/--timeout flag). No API key or network credentials are required.
interactive-mcp FAQ
Does this need an API key?
No. interactive-mcp requires no API key or credentials. It runs locally over stdio via npx.
Can it run remotely?
No. It is designed to run locally alongside the MCP client because it needs direct access to the user's operating system to display notifications and command-line prompts.
How do I change the prompt timeout?
By default prompts time out after 30 seconds. Add the -t (or --timeout) flag followed by a number of seconds to the args array in your client config, e.g. "args": ["-y", "interactive-mcp", "-t", "30"].
Can I disable some of the tools?
Yes. Use the -d (or --disable-tools) flag with a comma-separated list. Options are request_user_input, message_complete_notification, and intensive_chat. Disabled tools are not advertised or registered by the server.
Alternatives to interactive-mcp
Compare all alternatives →
AI-powered task-management system for AI-driven development that drops into Cursor, Windsurf, Claude Code, and more.
Background computer-use MCP server that drives native macOS, Windows, and Linux desktop apps without stealing focus.
Self-hosted MCP server for Jira and Confluence Cloud and Server/Data Center.
Compare interactive-mcp with: