Pressing Enter to accept an MCP tool call approval request does not work. The keyboard shortcut for accepting MCP approvals appears broken in the current Cursor version, even though a similar issue with “Enter to accept command” was previously fixed in an update.
Steps to Reproduce
Configure an MCP server in Cursor (e.g., GitHub MCP or Chrome DevTools MCP).
Trigger an agent action that requires MCP tool call approval.
When the MCP approval prompt appears, press Enter to accept.
Observe that the approval is not accepted and the action does not proceed.
Expected Behavior
Pressing Enter on an MCP tool call approval request should accept/approve the MCP call, consistent with how Enter-to-accept works for terminal command approvals.
A similar bug existed in an older version where Enter did not accept terminal command approvals; that was fixed in a subsequent update. The same keyboard shortcut is still broken specifically for MCP tool call approvals. Workaround: use the mouse/UI accept button instead of Enter.
Hey, thanks for the report, I can reproduce it. Enter-to-accept is currently only wired up for terminal command approvals, and the same keybinding hasn’t been added to MCP tool call approvals yet. So it’s not a regression, it’s a coverage gap, which is why it behaves differently from the terminal commands you remember.
I’ve filed an internal report. I can’t share an ETA yet, but I’ll post an update in the thread once I have one.
For now, two workarounds:
Click the Run or Accept button with your mouse, like you found.
If you call a specific MCP tool a lot, add it to the Allowlist so future calls run without confirmation.
Thanks @deanrie — that makes sense, and good to know it’s a coverage gap rather than a regression.
Both workarounds work for me (mouse click and allowlist).
One extra detail that might help when wiring up Enter for MCP approvals: **Enter alone does not accept**, but **Tab once, then Enter does work**. So it may be a focus issue on the accept action rather than Enter being completely unhandled.
Great detail, thanks. Tab then Enter suggests the default focus isn’t on the Accept button, not that Enter isn’t handled at all. That’s a helpful nuance, so I added it to the report.
When there’s an update on the fix, I’ll reply in the thread. Glad both workarounds worked for you.