MCP elicitation/create hangs Agent on Windows in Cursor 3.10.20, but works on macOS

[Arturo_Rodriguez]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Where does the bug appear?

Cursor IDE → Agent → MCP tool calls using elicitation

Description

MCP elicitation appears broken in Cursor 3.10.20 on Windows.

When an MCP tool call causes the server to send an elicitation/create request, Cursor does not display the elicitation UI. The tool call and Agent conversation remain pending until manually cancelled, Cursor is reloaded, or the server-side timeout is reached.

The same MCP server and tool flow work correctly with Cursor on macOS. They also worked in older Cursor versions.

This appears related to an earlier report that is now closed:

MCP Elicitation with HTTP OAuth hangs with request timed out error

MCP Elicitation seems to be broken after update to 1.6 . It was working in previous version though I don’t remember what was it. ```python class AudienceSelection(BaseModel): audience: str = Field(*description*="Target audience", *json_schema_extra*={"enum": \["developer", "business", "product", "ELI5"\]}) print(“Eliciting audience…”) result = *await* ctx.elicit( message=“Select the target audience (developer, business, product, ELI5)”, schema=AudienceSelection, ) p…

The issue is therefore either still present or has regressed specifically on Windows.

Environment

• Cursor: 3.10.20
• Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
• Architecture: x64
• OS: Windows 11, build 26200
• MCP transport: Stateful Streamable HTTP
• MCP SDK: .NET ModelContextProtocol 1.4.1
• Elicitation type: Form elicitation

Steps to reproduce

1. Connect Cursor to a Streamable HTTP MCP server that supports elicitation.
2. Confirm that the server connects and that its tools are listed successfully.
3. Invoke a tool that requires user approval.
4. During the tool call, have the MCP server send an elicitation/create request using ElicitAsync.
5. Observe the Agent conversation.

A simplified server-side flow is:

var result = await server.ElicitAsync(new ElicitRequestParams
{
    Message = "Approve calling this tool?",
    RequestedSchema = new ElicitRequestParams.RequestSchema
    {
        Properties =
        {
            ["reason"] = new ElicitRequestParams.StringSchema
            {
                Title = "Reason",
                MaxLength = 200,
            },
        },
    },
}, cancellationToken);

### Steps to Reproduce

1. Connect Cursor to a Streamable HTTP MCP server that supports elicitation.

2. Confirm that the server connects and that its tools are listed successfully.

3. Invoke a tool that requires user approval.

4. During the tool call, have the MCP server send an `elicitation/create` request using `ElicitAsync`.

5. Observe the Agent conversation.

### Expected Behavior

Cursor should:

Advertise form elicitation support during MCP initialization.

Display the elicitation form when it receives elicitation/create.

Allow the user to accept, decline, or cancel.

Return the corresponding MCP elicitation result to the server.

Resume the pending tool call and Agent conversation.

### Operating System

Windows 10/11

### Version Information

Version: 3.10.20 (user setup)

VS Code Extension API: 1.125.0

Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0

Date: 2026-07-07T07:03:33.071Z

Layout: IDE

Build Type: Stable

Release Track: Default

Electron: 40.10.3

Chromium: 144.0.7559.236

Node.js: 24.15.0

V8: 14.4.258.32-electron.0

xterm.js: 6.1.0-beta.256

OS: Windows_NT x64 10.0.26200

### For AI issues: which model did you use?

Opus 4.8

### Does this stop you from using Cursor

Yes - Cursor is unusable

[Colin]

Hi @Arturo_Rodriguez!

This is mostly a known bug related to having multiple windows opened, and not related to Mac vs. Windows.

MCP elicitation does not render in the Cursor Agents window on macOS

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug MCP elicitation does not render in the Cursor Agents window on macOS. When an MCP tool sends an elicitation request, no elicitation UI appears, and the tool call eventually times out. Cursor version: 3.6.31 (Universal) VS Code Extension API: 1.105.1 Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60 Date: 2026-05-31T17:46:29.630Z Layout: glass Build Type: Stable Release Track: Default Electron: 39.8.1 Chromium: 142…

Can you have a look? Happy to tie this thread to that existing internal bug report if it’s the same issue.

[Arturo_Rodriguez]

Hey Colin! Thanks for your response. I think it’s not related to that particular bug you mentioned. In this case, I had just one Cursor IDE instance opened. I tested the use case against different MCPs that sent Elicitations and Cursor always hangs. However, my teammates who use macOS didn’t have this problem.

Happy to send more information if needed!