fix: don't constrain MCP server to single project

Removed --project flag from MCP server startup args. The flag sets
BASIC_MEMORY_MCP_PROJECT env var which constrains ALL tool calls to
that project, ignoring explicit project params from tools.

Now relies on BM config's default_project for the default, while
allowing cross-project access (cloud or local) via the project param.

Author: bm-clawd

bm-client.ts

@@ -301,7 +301,7 @@ export class BmClient {
   private async connectFresh(): Promise<void> {
     const transport = new StdioClientTransport({
       command: this.bmPath,
-      args: ["mcp", "--transport", "stdio", "--project", this.project],
+      args: ["mcp", "--transport", "stdio"],
       cwd: this.cwd,
       env: this.env,
       stderr: "pipe",

tools/search.ts

@@ -54,7 +54,8 @@ export function registerSearchTool(
         },
       ) {
         const limit = params.limit ?? 10
-        log.debug(`bm_search: query="${params.query}" limit=${limit}`)
+        log.debug(`bm_search: query="${params.query}" limit=${limit} project="${params.project ?? "default"}"`)
+
 
         const metadata =
           params.metadata_filters || params.tags || params.status