User Prompt MCP Server

User prompt mcp mcp server lets Claude, Cursor and other MCP clients work with User Prompt MCP directly. A Model Context Protocol (MCP) server for Cursor that enables requesting user input during generation. This is mostly AI-generated code.

What User Prompt MCP does

A Model Context Protocol (MCP) server for Cursor that enables requesting user input during generation. This is mostly AI-generated code.

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.

Key capabilities

• 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

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

• Prerequisites — The Prerequisites tool exposed by this server
• Configuration — The server can be configured using command-line flags or environment variables:

Installing the user prompt mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

The server reads one environment variable: USER_PROMPT_TIMEOUT. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• For GUI functionality: - Linux: zenity - macOS: osascript (built-in)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. User Prompt MCP sits in that group, and the shape of its toolset — Prerequisites, Configuration — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by nazar256, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the user prompt mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.