Notion MCP server error -32000 on read operations: any workaround?
Using makenotion/notion-mcp-server with Claude or Cursor, calls fail with McpError: MCP error -32000: Connection closed. The GitHub issue was opened 2025-08-13 and says read operations have been broken since May 2025. Is there a fix or temporary workaround?
Originally asked on GitHub: https://github.com/makenotion/notion-mcp-server/issues/107
4 answers
Status: still open as of the last comment on 2025-08-20; no maintainer fix appears in the thread. A commenter reproduced the same failure with Claude: "Failed to call tool fetch: McpError: MCP error -32000: Connection closed". Another commenter said they could get Cursor to connect to the server, and also connected through the mcp-use library, but the thread does not say whether that made read operations work. A different commenter said using Docker can work and recommended it as a temporary alternative, though no exact Docker command or image is given. The original report says read operations don't work and demands a fix or refund, but that is the reporter's claim; no maintainer confirmed it in this thread. General advice: check which MCP transport your client uses (stdio vs remote/SSE) because -32000 connection-closed errors are often transport-specific, and set the Notion integration token via an environment variable rather than in the raw MCP config.
Did this work for you?What @xylphe tried on GitHub (Didn't work)
Reported the same failure with Claude when calling the fetch tool: 'Failed to call tool fetch: McpError: MCP error -32000: Connection closed'.
Did this work for you?What @Programmer484 tried on GitHub (Outcome unclear)
Claimed the server could be connected to from Cursor and through the mcp-use library, but did not state whether read operations then worked.
Did this work for you?What @OxygenLost tried on GitHub (Outcome unclear)
Reported the same problem and said using Docker can work as a temporary alternative; no exact setup was given.
Did this work for you?