About User Prompt MCP
User Prompt MCP is an MCP server for Cursor that lets the AI ask the user for input during generation without ending the response. It targets Cursor users who want an interactive loop with the model, and the code is mostly AI-generated.
Key features
- 01Requests user input during generation
- 02Dialog box with text wrapping
- 03Works on Linux and macOS
- 04Stdio transport for Cursor integration
- 05Configurable wait timeout
Use cases
- 01Asking the user a question mid-generation and then continuing
- 02Requesting confirmation when the agent is stuck or finishes a task
MCP support
This is an MCP server that exposes the input_user_prompt tool to MCP clients such as Cursor, so they can collect user responses.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEUser Prompt MCP
A Model Context Protocol (MCP) server for Cursor that enables requesting user input during generation. This is mostly AI-generated code.
Overview
This project implements an MCP server that allows Cursor (or any MCP-compatible client) to request additional input from users during model generation without ending the generation process. It serves as a bridge between the AI model and the user, creating a more interactive experience.
Features
- User Input Prompting: Allows the AI to ask for more information during generation
- Simple GUI: Presents input prompts in a dialog box with text wrapping
- Cross-Platform: Should work on both Linux (tested) and macOS
- Stdio Transport: Integration with Cursor via stdio
Installation
Prerequisites
- For GUI functionality:
- Linux: zenity
- macOS: osascript (built-in)
Quick Install (Recommended)
The easiest way to install user-prompt-mcp is using our installation script, which automatically downloads the appropriate binary for your system:
# Install the latest version
curl -sSL https://raw.githubusercontent.com/nazar256/user-prompt-mcp/main/install.sh | bash
# Or install a specific version
curl -sSL https://raw.githubusercontent.com/nazar256/user-prompt-mcp/main/install.sh | bash -s -- -v v1.0.0
The installation script will:
- Detect your OS and architecture (Linux or macOS, amd64 or arm64)
- Download the appropriate pre-compiled binary
- Install it to a suitable directory in your PATH
- Make it executable
Install from source
If you prefer to build from source (requires Go 1.18+):
go install github.com/nazar256/user-prompt-mcp/cmd/user-prompt-mcp@latest
Manual Installation
You can also download pre-compiled binaries directly from the Releases page.
Usage with Cursor
- Open Cursor and go to Settings
- Navigate to the MCP Servers section and add a new server by editing JSON:
{
"mcpServers": {
"prompt": {
"command": "user-prompt-mcp"
}
}
}
-
Save and refresh
-
Add to global rules something like: "Important - do not finish responding until explicitly told to do so, instead always use MCP
input_user_promptand wait for response in all cases, either you feel stuck, you have question or you finished work on a prompt - always communicate with the user using this MCP."
Configuration
The server can be configured using command-line flags or environment variables:
Timeout Configuration
By default, the server will wait 20 minutes for user input before timing out. You can customize this timeout using:
- Command line flag:
--timeout <seconds>user-prompt-mcp --timeout 600 # Set timeout to 10 minutes - Environment variable:
USER_PROMPT_TIMEOUT=<seconds>export USER_PROMPT_TIMEOUT=1800 # Set timeout to 30 minutes user-prompt-mcp
Now when using Cursor, the AI can request additional input from you without ending its generation.
License
MIT
Acknowledgements
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.