MCP Elicitation with HTTP OAuth hangs with request timed out error

Support Bug Reports
1

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,

)

print(“Elicitation result:”, result)
```

The tool call is stuck in `await ctx.elicit …`

```
Version: 1.6.26
VSCode Version: 1.99.3
Commit: 6af2d906e8ca91654dd7c4224a73ef17900ad730
Date: 2025-09-16T17:12:31.697Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0
```

1 Like
Cursor v1.6 - Release Discussions
2

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have a custom http OAuth implementation of MCP server.
In the server tool, I use the server.server.elicitInput(...) where server is coming from const server = new McpServer(...);
When the cursor chat/agent try to call my mcp tool, it always results in “MCP error -32001: Request timed out”

Steps to Reproduce

  • create a MCP server with http oauth
  • create a tool with elicitation input
  • try to call the tool with cursor chat/agent

Expected Behavior

The server.server.elicitInput() should not results in “MCP error -32001: Request timed out”

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.26 (Universal)
VSCode Version: 1.99.3
Commit: 6af2d906e8ca91654dd7c4224a73ef17900ad730
Date: 2025-09-16T17:12:31.697Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0

For AI issues: which model did you use?

Sonnet 4, GPT 5, Gemini 2.5 Pro

Additional Information

I try to use Visual Studio Code and it works flawlessly

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

I’m actually have the same experience, the elicitation doesn’t work anymore.
Here’s my full issue MCP Elicitation with HTTP OAuth hangs with request timed out error

1 Like
4

hi @rrifandani and @tsenov thank you both for the bug report details. I combined your posts as they are about same issue.

Could you add a Request ID with privacy disabled so we can look into the details? Getting a Request ID | Cursor Docs

Please also let me know which MCPs you use and if there is a public link to either MCP or repo we can check out.

Does the timeout occur also if user answers immediately?

5

I have the same problem with an stdio MCP server

6

Is this fixed? We have to downgrade to 1.5 to be able to use mcp elicitation right now, really hope this gets a patch soon so we can use the latest version.

8

Currently not yet, but will check the issue again with the team.

9

Thanks @condor. I can confirm this happens with all MCP servers, regardless of its transport mechanism. Every single elicitation request just breaks that agent chat.

I don’t mean to be harsh, but come on guys, any decent test suite should have caught this before it reached production.

10

@trevorSmart thank you for the update. Team has it on their shortlist.

1 Like
11

Hello,
I can confirm that it works on Cursor 1.5, but is broken since the 1.6 and even on the 1.7.39.
The MCP elicitation is working correctly on VSCode, but when I try using the tool (that is listed on MCP list), it says the tool is not available. When I ask LLM to list tools available, it lists all the tools except ones using elicitation.

12

Thanks for the info, we’re looking into it.

13

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.