Notion MCP server: notion-update-page fails in Cursor/Gemini/Kilocode - where is the fix?
The Notion MCP server's notion-update-page tool fails in Cursor: it never receives the correct arguments, and the generated data payload always starts with empty curly braces "{}". The same failure appears in Gemini and Kilocode after Notion's September 2025 API update. Where can I get a working version?
Originally asked on GitHub: https://github.com/makenotion/notion-mcp-server/issues/131
6 answers
Fixed in the community fork @mieubrisse/notion-mcp-server, which has merged PRs #180 and #173. The upstream makenotion/notion-mcp-server repo has no official fix in this thread, and one commenter suggests the project may be unmaintained.
To get notion-update-page working, switch to the fork instead of the original package. Use the npm package @mieubrisse/notion-mcp-server or the GitHub repository mieubrisse/notion-mcp-server. The fork maintainer states that database PostPage and UpdatePage now work after merging those PRs.
The thread does not confirm a root cause. One commenter suspected a connection to Notion's 2025-09-03 API update, but that is only a guess. Another user observed that the MCP tool definition makes the model emit a payload starting with "{}" regardless of instructions, so prompt-level workarounds did not help. No configuration change, CLI flag, or prompt workaround is documented in the thread; the fix is in the tool implementation itself.
General advice: if the fork does not suit your workflow, look for another actively maintained Notion MCP server, as one commenter recommended. The fork maintainer also warns they will only fix their own workflows and review bugfix PRs, not implement feature requests.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
The reporter called notion-update-page in Cursor and tried repeatedly to coax the model into passing the correct arguments, but the tool never received them.
Source: https://github.com/makenotion/notion-mcp-server/issues/131 (opens external site)
Did this work for you?What @sbarnsley tried on GitHub (Didn't work)
A user found the generated payload always begins with "{}" no matter what structure is requested. Prompting the model to validate and fix the JSON did not help because it follows the MCP tool definition.
Did this work for you?What @PaxVolumi tried on GitHub (Outcome unclear)
A commenter suspected the failure was caused by Notion's 2025-09-03 API update and linked the official upgrade guide, but this was not confirmed in the thread.
Did this work for you?What @danielostrow tried on GitHub (Outcome unclear)
A commenter said they had fixed a similar problem and hoped the fix would be merged, but provided no details or commands.
Did this work for you?What @mieubrisse tried on GitHub (Worked)
The maintainer of @mieubrisse/notion-mcp-server merged PRs #180 and #173 and stated that database PostPage and UpdatePage now work in the fork.
Did this work for you?