The PR introduces an optional `all_projects` boolean to MCP `mem_search`, enabling true global search across projects, while preserving the existing single-project default when the flag is omitted or false.
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
It extends the MCP search schema with `all_projects` and changes `handleSearch` to bypass project resolution only when that flag is true, so the search backend can return global results while retaining legacy per-project behavior by default.
Developers and operators using `mem_search` can now run cross-project memory lookups in one call, which removes the need to manually target projects one by one when investigating or aggregating context across projects. Technically, the MCP layer now treats `all_projects=true` as a signal to skip project-scoped resolution and query broadly, but keeps default and explicit `false` behavior unchanged; after merge, monitor for authorization boundary behavior and any increase in result size or latency for large multi-project deployments.
Developers and operators using `mem_search` can now run cross-project memory lookups in one call, which removes the need to manually target projects one by one when investigating or aggregating context across projects. Technically, the MCP layer now treats `all_projects=true` as a signal to skip project-scoped resolution and query broadly, but keeps default and explicit `false` behavior unchanged; after merge, monitor for authorization boundary behavior and any increase in result size or latency for large multi-project deployments.