Notion Developers Updates & Release Notes

Partial update_content edits return warnings

When some update_content edits match and others don’t, Update page markdown and the notion-update-page MCP tool now apply the edits that match and list each miss in warnings with code no_match, or indentation_mismatch when the text is on the page with different indentation. This works for both markdown versions. The request fails only when no content-changing edit matches. Before, REST skipped misses without saying so, and MCP failed the whole call. See Update warnings.

Return fewer page properties from search

Search now accepts the filter_properties query parameter, so you can return only the page properties you need. It works like it does on data source queries, except that search skips names or IDs that don’t exist on a page.

List page backlinks in Notion MCP

The new notion-list-page-backlinks tool lists the pages in the same workspace that link to or mention a page or database. It returns IDs, titles, and URLs, and only for pages the user can open. See List page backlinks.

Look up permission groups in Notion MCP

The new notion-get-groups tool lists the permission groups a user can see, with their IDs and names. People properties show a group only as space_permission_group-, so assistants can now turn that ID into a name, or find a group by name before setting it. See Get groups.

Delete pages and databases in Notion MCP

Two new Notion MCP tools move content to Trash after the user confirms. notion-delete-pages moves up to 20 pages, and notion-delete-databases moves up to 20 databases with their rows. Both need the update content capability. Locked pages and databases can’t be moved to Trash. To undo a deletion, use notion-restore-pages or restore the item from Trash in Notion. See Supported tools.

Edit, delete, and react to comments in Notion MCP

Four new Notion MCP tools change existing comments. notion-update-comment replaces the text of a comment the user wrote, and notion-delete-comment deletes one. notion-set-discussion-resolved resolves or reopens a discussion. notion-set-comment-reaction adds or removes the user’s emoji reaction. The tools need a Business or Enterprise plan. Get comment and discussion IDs from notion-get-comments or notion-create-comment. See Supported tools.

Data source schema update fixes

Update a data source now changes the color of an existing select, multi_select, or status option instead of returning a validation_error. Option names also match existing options without regard to case, so sending high keeps the existing High option and its ID instead of replacing it. See Existing select options.

Property updates now keep the existing description when you omit it, for every property type and when you change a type. Send null to clear it. The same rule applies to an option’s own description. Omitting options on a select or multi_select update now keeps the current options. See Update data source properties.

Admin API list endpoints accept start_cursor

List MCP client connections and List personal access tokens now accept start_cursor, like other Admin API list endpoints. Before this change, these endpoints ignored start_cursor and returned the first page again. The cursor parameter still works but is deprecated. If you send both with different values, the request fails with a 400 error.

notion-download-skill returns markdown for Skills without files

When a Skill has no supporting files, notion-download-skill in Notion MCP now returns markdown, the full SKILL.md text with its frontmatter, instead of a url to an archive. Skills with supporting files still return a signed url. See Use Notion Skills with MCP.

One search tool in Notion MCP

Hosted Notion MCP sessions now list one content-search tool, notion-search (search for OpenAI clients). Its description matches the user’s AI search access. It describes AI search when the user has it, and keyword search otherwise, with a one-line upgrade note when the plan lacks AI search. notion-ai-search no longer appears in tools/list, but it stays callable by name, so clients with a cached tool list keep working. Workspace-owned MCP connections, which have a selected tool list, keep the earlier tool list and descriptions. In the other sessions, the server instructions also tell clients to use the Notion search tool for every content search.

notion-get-tool-access is optional

Except on workspace-owned connections, tool descriptions no longer tell clients to call notion-get-tool-access before they use a tool. Tools apply access limits themselves and report them in their results. Call notion-get-tool-access only when you want plan or parameter details up front. This replaces the September 17, 2026 advice to call it first.

OpenAI’s search and fetch shape for ChatGPT

For ChatGPT connections, a content search with search returns { results: [{ id, title, url }] } and fetch returns { id, title, text, url, metadata }, as both structuredContent and JSON text. This is the shape that OpenAI’s MCP requirements set for company knowledge and deep research. ChatGPT search results no longer include highlights, path, timestamps, or notices. When fetch gets include_file_urls: true, file download URLs are under metadata.references. User lookups and other clients don’t change; see Supported tools.

Status group filters beta

Status filters can now match groups with group_equals and group_does_not_equal. These operators remove option and group name ambiguity.

Send Notion-Beta: status-group-filters-2026-10-06 to opt in. With the header, equals and does_not_equal match only option names. Views return saved group filters with group operators. Without the header, nothing changes. See Status group filters beta.

Warnings from notion-update-page

notion-update-page now returns an optional warnings array, for direct and queued updates, when it changed or ignored part of the input, such as lines dropped for incorrect indentation or text auto-corrected to match the page. Each warning has a code and a message, and Markdown parser warnings also carry category and autofix. Each message is at most 500 characters; a longer one is cut and ends with a note giving its original length. A clean update has no warnings key; see Supported tools.

No more tool-specific Notion MCP rate limits

notion-search and notion-query-data-sources no longer have their own rate limits. Calls to these tools now count toward the standard request limits, like other Notion MCP tools. See Supported tools.

Create teamspace root pages with Notion MCP

notion-create-pages now supports creating pages directly in a teamspace with parent.teamspace_id. Use a user-backed connection with permission to add top-level pages; see Teamspace root pages for details and an example.

Page edits return 400 when a page is too large to load

Update a page’s content as markdown and the notion-update-page MCP tool now return HTTP 400 validation_error when a page is too large to load in full (about 20,000 records, most of them blocks) and the edit targets a block that wasn’t loaded or would remove content that wasn’t loaded. Before, they returned HTTP 500 internal_server_error. Retrying the same request fails the same way. Content that wasn’t loaded appears as tags when you retrieve the page as markdown, so edit only content outside those tags. The response’s additional_data.limit_kind is page_record_count, and additional_data.limit holds the limit.

Custom blocks in markdown

The markdown content API and Notion MCP now read custom blocks with inherited bindings as <custom-block definition-id="…" url="…" /> instead of <unknown>. You can place existing definitions and preserve unchanged instances during page edits; see Working with markdown content. Definition creation remains in private alpha.

New SIEM event for the AI meeting notes consent setting

The SIEM and DLP event stream now sends workspace.settings.meeting_notes_consent_setting_updated when an admin changes whether a workspace requires consent before AI meeting notes transcription. The payload carries the final state, either enabled or disabled. See SIEM events.

This is separate from the existing audit log entry for a person confirming consent in a meeting. The new event records a change to the requirement, not an instance of consent.

Preview: Notion-flavored Markdown with markdown_version

The markdown endpoints accept a new optional markdown_version parameter. Set it to v2 to read and write Notion-flavored Markdown. This is an opt-in preview: v1 (enhanced markdown) stays the default, and requests without the parameter work as before. Synchronous v2 updates return parser warnings. Sending markdown_version without markdown on POST /v1/pages or the comment endpoints returns a 400 validation_error. See Markdown versions and the Notion-flavored Markdown format reference.

Rate limit waits in the response body

Any 429 or 529 response that includes a Retry-After header now repeats the wait in the body as additional_data.retry_after, so clients that can’t read headers, such as MCP clients, can still see how long to wait. Two new rate_limit_reason values identify an endpoint’s own limit (public_api_endpoint_rate_limit) and a connection whose API access has been restricted (public_api_request_blocked). A workspace-limit 429 now says that the limit is shared by all of the workspace’s connections. See Request limits.

Page writes return 504 when a request times out

Update a page’s content as markdown and the notion-update-page MCP tool now return HTTP 504 gateway_timeout when a request runs past its deadline. Before, they returned HTTP 500 internal_server_error. The notion-create-pages and notion-convert-page-to-skill MCP tools already returned 504 in this case. A 504 does not mean the write was undone, so check whether the change was saved before you retry it. A write that runs out of its time budget still returns 503 service_unavailable, with additional_data.retry_guidance. See Request limits for when to retry each status.