Cloud MCP should inherit default project from UI settings

[mikrub]

Summary

When using Basic Memory Cloud's remote MCP (via claude.ai, Claude Desktop connectors), the project parameter is required on every tool call. Setting a "default project" in the web UI (app.basicmemory.com) does NOT propagate to MCP API calls.

Request: MCP should inherit the default project from the user's UI/account settings when the project param is omitted.

Environment

• basic-memory: 0.17.9
• Using cloud MCP via claude.ai

Steps to Reproduce

1. Set default project to my-notes in app.basicmemory.com
2. In claude.ai, ask Claude to "write a note"
3. Claude calls write_note without explicit project parameter
4. Error: "No project specified. Project is required for cloud mode."

Expected Behavior

The note should be created in my-notes (the user's default project from UI).

Current Workaround

Claude.ai can use its built-in memory (memory_user_edits) to persist the project preference. But this:

• Requires users to teach Claude about the preference
• Doesn't work for other LLM clients using the MCP
• Is fragile — new conversations may not have the memory context

Proposed Solution

The MCP server should:

1. Look up the authenticated user's default project setting from their account
2. Use that as fallback when project param is omitted
3. Explicit project param still overrides

Benefits

• Better UX: Users set preference once in UI, works everywhere
• Consistent behavior: UI and MCP behave the same
• Reduces prompt engineering: LLMs don't need memory hacks to remember project
• Multi-client support: Any MCP client benefits, not just Claude

Context

I'm using Basic Memory across the full Claude ecosystem (Claude Code, Desktop, claude.ai, mobile). The cloud MCP is essential for web/mobile access. Having to specify project on every call adds friction, especially when the UI already has this setting.