Skip to main content

Notion MCP is error prone

Feature Requests

Hi Daniel, i have quite a few issues with the notion MCP Server. Sometimes it works quite well, sometimes it doesn’t at all. I have one MAC that usually can connect successfully, but has to reauthenticate every few hours. Linear seems to be able to refresh its authentication, but notion doesn’t.

On another Mac i’m completely unable to authenticate and always get:

Failed to fetch access token: Auth code must be a valid UUID (invalid_request) from Notion, while the setup browsers, etc. are all the same.

Thank you and best regards, Max

Posted by Maximilian Christl ·
Status: Completed3 comments

Log in to comment and vote

Comments3

  • Daniel Nguyen changed status to Completed
    Team•

    Apr 28

    Pinned

    I’ve fixed this in v2.11. Can you confirm? I’ll share more on the other issue.

  • Maximilian Christl

    •

    May 1

    Hi Daniel, after testing it for several days, most issues are now fixed, especially the authentication issue. Thank you very much for this.

    The only remaining issue with Notion MCP is the one we discussed: the instruction resources referenced by the MCP instructions are not accessible to the LLM because resource support is still missing.

    This has been discussed in a separate ticket, but is still negatively affecting the notion connector.

    Thank you very much for putting in the effort to fix the other issues.

  • Daniel Nguyen

    Team•

    Apr 27

    I think I’ve found the root cause. I think we should track this issue in the bigger ticket at

    https://feedback.boltai.com/p/issues-with-mcp-servers

    I wasn’t able to reproduce the issue but I think there might be some cached config on your second Mac that caused the issue. Can you try delete the cached config (screenshot below) and authenticate again.

    But even so, it probably will be reset after an hour or so. The culprit is a mixed of a few different things: BoltAI implemented an old draft spec, and it doesn’t store the DCR’s client_id if the server doesn’t respond with a valid client_secret.

    Which effectively makes every new refresh token request come with a brand new client (in the perspective of the MCP server), thus, requiring a new auth session.

    Will release a new version soon.