delete_project missing workspace parameter for cross-workspace targeting

[phernandez]

Summary

delete_project has no workspace or project_id parameter, so it can only find and delete projects in the default workspace. Projects created in non-default workspaces via create_memory_project(workspace="big-team") cannot be deleted through MCP.

Steps to Reproduce

1. Create a project in a non-default workspace: create_memory_project(project_name="test-project", project_path="/test-project", workspace="big-team")
2. Try to delete it: delete_project(project_name="test-project")

Expected Behavior

Either:

• A workspace parameter (like create_memory_project has) allows targeting the correct workspace
• Or the tool searches across all accessible workspaces

Actual Behavior

Error: Project 'test-project' not found. Available projects: main, getting-started, moby-dick

Only lists projects from the default workspace.

Notes

• create_memory_project already has a workspace parameter — delete_project should have parity
• Other tools use project_id for cross-workspace targeting, which could also work here

[claude]

Claude finished @phernandez's task in 4m 39s —— View job • claude/issue-800-20260508-0212 • Create PR ➔

---

Issue Triage & Implementation

Classification: Enhancement (MCP tool parity) | Priority: Medium | Component: MCP tools | Complexity: Simple

• Analyze issue
• Investigate current delete_project and create_memory_project implementations
• Add appropriate labels (enhancement)
• Implement fix: add workspace parameter to delete_project
• Write tests (3 new unit tests)
• Commit and push changes

---

Changes Made

src/basic_memory/mcp/tools/project_management.py

• Renamed private helper _resolve_create_project_workspace → _resolve_workspace_routing so it can be shared by both tools
• Added workspace: str | None = None parameter to delete_project, matching the signature of create_memory_project
• delete_project now resolves the workspace selector (slug/name/tenant_id) and passes it to get_client(), routing the list and delete requests to the correct workspace

tests/mcp/test_tool_project_management.py

• test_delete_project_resolves_workspace_slug — cloud mode: slug resolves to tenant_id passed to get_client
• test_delete_project_workspace_is_local_noop — local mode: workspace passed through unchanged, no cloud resolution
• test_delete_project_default_workspace_is_none — no workspace arg: get_client receives workspace=None (uses default)

Usage after this fix:

# Before: only worked for default workspace
delete_project("test-project")

# After: can target any workspace by slug, name, or tenant_id
delete_project("test-project", workspace="big-team")

[groksrc]

While validating the #788 fix today (2026-05-07), reproduced this on Dev:

1. `create_memory_project(project_name="mcp-validation-788", project_path="/test/validation-788", workspace="drew-cain")` succeeded — project landed in drew-cain workspace as expected (create_memory_project has no way to target a non-default workspace #788 working).
2. `delete_project(project_name="mcp-validation-788")` failed with: `Project 'mcp-validation-788' not found. Available projects: main, getting-started`.

The error message confirms the diagnosis in this issue: `delete_project` only saw projects from the connection's default workspace (Personal), not from drew-cain where the project actually lives. The test artifact (external_id `859ee1b3-c20d-4b7f-add6-7ded42c4815c`) is now stranded in drew-cain with no MCP-surface way to remove it.

So #788 + this issue together cover the full create/delete lifecycle gap — fixing this would also unblock cleanup of any test artifacts created via the now-working `workspace=` parameter on `create_memory_project`.