AI search accepts filters, and notion-search routes content queries to it
Editor, teamspace, and status filters still need a Business or Enterprise plan, and routing depends on what the connection supports.
Notion's Notion MCP server now lets notion-ai-search accept the same exact filters and sort options as notion-search, plus an empty query for filter-only browsing, according to the changelog. Using either restricts results to the Notion workspace only, though the response still reports type "ai_search". Leaving them out searches Notion and connected sources together.
- Filtering by editor, last-edited date, multiple teamspaces, title only, or content status, and sorting by date, still require a Business or Enterprise plan.
- User lookup by name or email stays on notion-search with query_type "user".
- Content queries sent to notion-search now run through AI search automatically when the connection supports it, so clients that haven't switched to notion-ai-search still get unified results across Notion and connected apps. A query with an exact filter, an empty query, or a non-relevance sort stays on plain workspace search, and a connection that can't use notion-ai-search keeps its content searches on workspace search too.
The legacy content_search_mode: "ai_search" parameter now returns a permission error on connections that can't use notion-ai-search. The 30-requests-per-minute limit on notion-search applies to these calls either way.
