Hey, thanks for the detailed report and screenshots. Here’s what’s happening: the error page that says Invalid MCP state. Please enable browser cookies and try again. is coming from Notion’s own server mcp.notion.com, after you click Continue. Part of the flow on Cursor’s side worked fine, the consent page, workspace selection, and the redirect to http://localhost:8787/callback (you can see it in the first screenshot). It fails at the Notion step.
What to try, in order:
In Cursor Settings > MCP > Notion, click Sign out or Clear authentication, then Authenticate again. This forces a fresh OAuth state and client registration.
Check that your default browser allows cookies for notion.com and notion.so (Notion stores its state in a cookie). You can also temporarily switch your default browser and try again there.
If the same error happens in different browsers or on different devices, the stuck state is likely on Notion’s side. In that case, contact Notion support and mention Invalid MCP state on mcp.notion.com. Only they can clear it.
Workaround if OAuth won’t work at all: Notion MCP can take a personal access token via the Authorization: Bearer header in a custom MCP config, which fully bypasses OAuth.
Let me know how it goes. If it still fails after re-auth and checking cookies, share an update and we’ll dig deeper.
