-
Notifications
You must be signed in to change notification settings - Fork 245
Open
Description
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_PATHenvironment variableMCP_WORKSPACE_FOLDERenvironment 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.mdtoMCP Integration Guidewith 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_infotool- Verify workspace path is detected correctly
- Check if error messages are clear (not mentioning VS Code)
- Call
ace_onboardtool if not already onboarded- Verify
.ace/.ace.jsonis created - Check workspace name is derived correctly
- Verify
- Call
ace_retrievewith a code-related query- Verify both code context AND memory context are returned
- Check that retrieval works for the workspace
Acceptance Criteria
- Workspace detected via
list_roots()(no env vars needed) - Auto-onboarding creates
.ace/.ace.jsonwith correct workspace name - Code retrieval returns workspace-specific results
- Error messages don't mention VS Code when workspace not found
- Documentation accurately reflects the tested client's setup
Additional Notes
- Qdrant must be running:
docker run -d -p 6333:6333 qdrant/qdrant - Required env vars:
VOYAGE_API_KEY,ZAI_API_KEY(orOPENAI_API_KEY) - Report findings as a comment or PR
Resources
ace_mcp_server.py- Workspace detection logicdocs/VSCODE_INTEGRATION.md- Client configuration examplesdocs/MCP_INTEGRATION.md- MCP protocol guide
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels