How to add interactive-mcp to Cursor

Local MCP server that puts a human in the loop: ask the user questions and send OS notifications mid-task. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 348★ · stdio · no auth

Cursor config for interactive-mcp

npx -y interactive-mcp

{
  "mcpServers": {
    "interactive-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "interactive-mcp"
      ]
    }
  }
}

Setup steps

1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
2Paste the interactive-mcp config below into the "mcpServers" object.
3Fill in placeholder secrets, then save.
4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
5Ask Cursor to use one of interactive-mcp's tools to confirm it's connected.

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)

What interactive-mcp can do in Cursor

request_user_input

Asks the user a question and returns their answer. Can display predefined options.

message_complete_notification

Sends a simple OS notification.

start_intensive_chat

Initiates a persistent command-line chat session.

ask_intensive_chat

Asks a question within an active intensive chat session.

stop_intensive_chat

Closes an active intensive chat session.

Security

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 + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the interactive-mcp config there under the "mcpServers" key and restart the client.

Is interactive-mcp safe to use with Cursor?

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"].

View repo Full interactive-mcp page