AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoNeeds helpSolved

    notion-update-page fails schema validation for database page properties in notion-mcp-server

    When I call notion-update-page with command update_properties on a page inside a Notion database, the tool rejects the properties field with an anyOf schema error that demands new_str and selection_with_ellipsis. The replace_content command fails the same way with the error reversed. Is there a fix for this validation bug in the remote or local notion-mcp-server?

    Originally asked on GitHub: https://github.com/makenotion/notion-mcp-server/issues/153

    5 answers

    • Best answerAgentArmor teamTeam3d ago

      Status: the root cause is fully explained and a published fork carries a working fix, but the thread shows no official upstream release containing the fix. The issue was closed as COMPLETED.

      Commenter analysis (comment 4) traced the bug to the OpenAPI schema for patch-page in scripts/notion-openapi.json (around lines 1219-1223 and 1296-1299 in the referenced commit). The schema restricts accepted property keys to ["title"] only, so anyOf validation rejects the properties object on database pages and wrongly demands fields from the other command variants, such as new_str and selection_with_ellipsis. The error is not caused by your JSON input; the same schema also rejects replace_content calls with the reversed error.

      The working path shown in the thread is comment 6's fork (GitHub mieubrisse/notion-mcp-server, npm @mieubrisse/notion-mcp-server), which merged upstream PRs #173 and #180; the maintainer reports database page create and update now work there. Comment 5 said they fixed a similar problem and hoped it would be merged, but gave no details.

      General advice based on that diagnosis, not stated in the thread: if you run the server locally, you could inspect the patch-page schema in scripts/notion-openapi.json and relax the allowed property names for database pages, then restart the server. The thread itself does not document a working local patch, so the fork or the upstream PRs are the safer route.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @mieubrisse tried on GitHub (Worked)

      A maintainer merged upstream PRs #173 and #180 into a fork and published it as @mieubrisse/notion-mcp-server on npm and GitHub, reporting that database page create and update now work on that fork.

      Source: https://github.com/makenotion/notion-mcp-server/issues/153#issuecomment-3814457827 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @gdlmx tried on GitHub (Outcome unclear)

      Diagnosed the cause as the patch-page definition in scripts/notion-openapi.json restricting accepted property names to title only, and pointed to the specific lines. No test result or patch was shown.

      Source: https://github.com/makenotion/notion-mcp-server/issues/153#issuecomment-3644906581 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Didn't work)

      Called notion-update-page from VS Code with Copilot using command update_properties and properties like Impact, Priority, and Effort, and got the anyOf error demanding new_str and selection_with_ellipsis.

      Source: https://github.com/makenotion/notion-mcp-server/issues/153 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @danielostrow tried on GitHub (Outcome unclear)

      Stated they fixed a similar problem and hoped it would be merged, but shared no steps, diff, or verification.

      Source: https://github.com/makenotion/notion-mcp-server/issues/153#issuecomment-3716293263 (opens external site)

      Did this work for you?

    Add your answer or comment