Objective
Test and verify ACE MCP server workspace detection and auto-onboarding with non-VS Code MCP clients (Claude Desktop, Cursor, etc.).
Context
The ACE MCP server uses the MCP list_roots() protocol for automatic workspace detection. The implementation in ace_mcp_server.py includes a 6-level fallback system:
- MCP
list_roots() protocol (primary)
ACE_WORKSPACE_PATH environment variable
MCP_WORKSPACE_FOLDER environment variable
- Project marker detection (
.git, package.json, pyproject.toml, etc.)
- Current working directory
- Invalid path exclusion (home, temp, drive roots)
Recent Changes
- Updated error messages to be client-agnostic (no longer mention "VS Code")
- Updated
VSCODE_INTEGRATION.md to MCP Integration Guide with client-specific configs
- Added Claude Desktop and Cursor configuration examples
Verification Steps
For each MCP client (Claude Desktop, Cursor, others):
- Install ACE MCP server in client's config
- Open a project folder in the client
- Call
ace_workspace_info tool
- Verify workspace path is detected correctly
- Check if error messages are clear (not mentioning VS Code)
- Call
ace_onboard tool if not already onboarded
- Verify
.ace/.ace.json is created
- Check workspace name is derived correctly
- Call
ace_retrieve with a code-related query
- Verify both code context AND memory context are returned
- Check that retrieval works for the workspace
Acceptance Criteria
Additional Notes
- Qdrant must be running:
docker run -d -p 6333:6333 qdrant/qdrant
- Required env vars:
VOYAGE_API_KEY, ZAI_API_KEY (or OPENAI_API_KEY)
- Report findings as a comment or PR
Resources
ace_mcp_server.py - Workspace detection logic
docs/VSCODE_INTEGRATION.md - Client configuration examples
docs/MCP_INTEGRATION.md - MCP protocol guide
Objective
Test and verify ACE MCP server workspace detection and auto-onboarding with non-VS Code MCP clients (Claude Desktop, Cursor, etc.).
Context
The ACE MCP server uses the MCP
list_roots()protocol for automatic workspace detection. The implementation inace_mcp_server.pyincludes a 6-level fallback system:list_roots()protocol (primary)ACE_WORKSPACE_PATHenvironment variableMCP_WORKSPACE_FOLDERenvironment variable.git,package.json,pyproject.toml, etc.)Recent Changes
VSCODE_INTEGRATION.mdtoMCP Integration Guidewith client-specific configsVerification Steps
For each MCP client (Claude Desktop, Cursor, others):
ace_workspace_infotoolace_onboardtool if not already onboarded.ace/.ace.jsonis createdace_retrievewith a code-related queryAcceptance Criteria
list_roots()(no env vars needed).ace/.ace.jsonwith correct workspace nameAdditional Notes
docker run -d -p 6333:6333 qdrant/qdrantVOYAGE_API_KEY,ZAI_API_KEY(orOPENAI_API_KEY)Resources
ace_mcp_server.py- Workspace detection logicdocs/VSCODE_INTEGRATION.md- Client configuration examplesdocs/MCP_INTEGRATION.md- MCP protocol guide