Plan mode can't access Notion MCP

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using Plan Mode with the Notion MCP server connected, any attempt to invoke a Notion tool (e.g. notion-fetch) fails with a validation error indicating that required arguments are undefined. Switching to Agent Mode instantly resolves the issue - the exact same tool call succeeds without any changes to the MCP configuration or prompt.

Steps to Reproduce

Connect the Notion MCP server in Cursor settings
Open a chat in Plan Mode
Ask cursor to fetch or interact with a Notion page (e.g. “fetch this Notion doc: …”)
Observe the error in the chat output
Switch to agent mode and ask to fetch again → success

Expected Behavior

Plan Mode should be able to invoke Notion MCP tools with correctly forwarded arguments, the same way Agent Mode does.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.0.12
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin x64 24.6.0

For AI issues: which model did you use?

auto

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. I see the screenshot with the error, this is a known issue.

During MCP tool auto-calls, the model sometimes doesn’t pass required args, and the call gets sent with an empty {}. This shows up more often in Plan Mode because it has a different set of available tools. A few users have hit the same thing across different MCP servers (GitHub, Linear, and others):

The team is aware. Until it’s fixed, the workaround is to use Agent Mode for MCP tool calls.

Let me know if you have any questions.

Hey, quick update on the thread: the fix has shipped, so MCP tool arguments should now pass correctly in Plan Mode. Update Cursor to the latest version and check again.

If you can still reproduce it, please start a new thread with your current version and the Request ID, and we’ll take a look.