Notion 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.

Your agents and teams run on context. If you switch agents, add a new tool, or welcome a new teammate, you shouldn’t have to explain everything again. With Notion, there’s a durable, shared place to remember what matters.

This update is all about context. Connecting data, tools, and skills so you’re free to use any agent or model.

With so many things changing, your context can stay in Notion.

Explore connections →

Connect your agents to Notion with MCP

Connect an MCP-compatible agent to Notion so it can read your workspace context and update docs and task trackers. Whether you use Claudes, Muses, GrokBots, Dots, or another agent, Notion gives them a shared place to find what they need, so you can switch agents without starting from scratch. Set up an agent with Notion →

And with Notion MCP controls, admins can see who connected each AI tool, check when it was last used, and revoke a person’s access without affecting other connections. Set up MCP controls →

Connect your Notion Agents to 150+ tools with MCP

Bring the tools your team already uses into Notion. MCP connections let Notion Agent and Custom Agents draw on context from those tools and take action across them. Create an account brief in Notion using HubSpot pipeline data, add Stripe billing details to a customer health review, or bring Cloudflare infrastructure details into a postmortem. And that’s just the start. Browse 150+ MCP connections →

Write a skill once. Use it with every agent.

Skills are the best way to teach agents how you work … and not just for engineers. Now, Notion is the best place to create, share, and keep them current. Sync your Skills across ChatGPT, Claude, and more with the new Skills API, which loads Skills from Notion into GitHub.

Already have Skills for your agents? Ask your agent to recreate them in Notion with MCP, then keep building your library there. Here’s a quick demo, and here are docs to learn more.

See every change by every person and agent

With agents and people making constant updates, version history has never been more important. So we’ve upgraded ours! You get a clearer record across pages and databases, with highlighted edits, detailed database changes, and attribution. Let your agents work while keeping their changes visible and secure. Review what changed, see who changed it, and restore prior versions with a quick click. Learn more →

Don’t pay twice. Use your ChatGPT plan in Notion.

Yes, you just read that right. If you have ChatGPT Plus or Pro, your subscription can now cover your AI usage in Notion. Just connect your plan, pick a GPT model, and go. We don’t add a markup. We just want you to have the best tools for the job, for the best price. Available for Business and Enterprise plans. Check out a quick demo and the docs.

Column permissions in databases

Notion databases give teams and agents a shared, up-to-date source of context. But both teams and agents need the right level of access. Column permissions were a top requested feature for years (we spent time getting this one right). They let database owners control which properties each person or agent can view or edit. Recruiting teams can collaborate on candidates without exposing compensation. Support agents can use account context without seeing restricted customer data. Watch the trailer from one of it’s creators!

Reintroducing synced databases

We rebuilt our synced databases, starting with GitHub, Jira, and Salesforce, so your teams and agents always work from the latest data. They’re faster, more reliable, and show a live health status for each sync. They work like any other Notion database, so you can add your own properties, create views, and trigger automations. At Notion, we build customer hubs by syncing Salesforce accounts and linking to meeting notes and feature requests, so every team works from the same current view of each customer. Learn more →

New week, new models

The labs are at it again. Seven new models all added, including GPT 6.1-Sol, GPT-6 Luna, Opus 5.5, and Sonnet 5.5. Use any of them knowing they’ll all know the latest about your team works.

And ICYMI, we’ve been evaluating how models perform across a range of knowledge-work tasks, using live anonymized traffic and judged by models. Check out our Knowledge Board →

More ways to connect and govern context

• Redesigned Connections settings: Search or browse by category, see how each tool connects, and preview example workflows. Admins can allow only tools verified by Notion or specific tools they choose.
• Notion notifications in Microsoft Teams: Get Notion mentions, comments, and access requests in Teams, then reply or respond without switching apps.

We can’t wait to see how Notion can be the backbone of your dock.

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.