Skip to content

[Good First Issue] Test ACE MCP server with non-VS Code clients #56

@erwinh22

Description

@erwinh22

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:

  1. MCP list_roots() protocol (primary)
  2. ACE_WORKSPACE_PATH environment variable
  3. MCP_WORKSPACE_FOLDER environment variable
  4. Project marker detection (.git, package.json, pyproject.toml, etc.)
  5. Current working directory
  6. 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):

  1. Install ACE MCP server in client's config
  2. Open a project folder in the client
  3. Call ace_workspace_info tool
    • Verify workspace path is detected correctly
    • Check if error messages are clear (not mentioning VS Code)
  4. Call ace_onboard tool if not already onboarded
    • Verify .ace/.ace.json is created
    • Check workspace name is derived correctly
  5. 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

  • Workspace detected via list_roots() (no env vars needed)
  • Auto-onboarding creates .ace/.ace.json with 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 (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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions