Is your feature request related to a problem?
Today the MCP server requires CODELOGIC_WORKSPACE_NAME. This is fine for single-workspace setups but is cumbersome for general IDE development where a user may switch between multiple CodeLogic workspaces. Manually exporting different env vars or restarting the MCP server to change workspaces slows the workflow and increases configuration friction.
Describe the solution you'd like
- Query the neo4cape server for the list of available workspaces using configured connection settings (e.g., NEO4CAPE_URL and auth).
- Provide an IDE-friendly, interactive selection flow via an MCP prompt/tool (e.g., “Select CodeLogic Workspace”), and cache the selection for the current session.
- Non-interactive behavior:
- If exactly one workspace is returned, auto-select it.
- Allow a default via config (e.g., CODELOGIC_DEFAULT_WORKSPACE) or a persisted selection file in the user’s config directory to avoid repeated prompts.
- Maintain backward compatibility: if CODELOGIC_WORKSPACE_NAME is set, skip discovery and use that value.
- Add structured logs for selection events and failure cases
Describe alternatives you've considered
- Keep requiring
CODELOGIC_WORKSPACE_NAME and document per-project shell profiles.
- Provide a CLI wrapper to set the env var and restart the server.
Additional context
No response
Priority
Important
Is your feature request related to a problem?
Today the MCP server requires CODELOGIC_WORKSPACE_NAME. This is fine for single-workspace setups but is cumbersome for general IDE development where a user may switch between multiple CodeLogic workspaces. Manually exporting different env vars or restarting the MCP server to change workspaces slows the workflow and increases configuration friction.
Describe the solution you'd like
Describe alternatives you've considered
CODELOGIC_WORKSPACE_NAMEand document per-project shell profiles.Additional context
No response
Priority
Important