Multi-Workspace Support
Each API key can access multiple isolated workspaces. By default, requests go to the workspace marked as default. Uselist_workspaces to discover all accessible workspaces (personal + organization).
When you only have one accessible workspace, list_workspaces explicitly tells the agent no switching parameter is needed and returns the current Undisk MCP server time alongside the current workspace ID.
Switching workspaces:
@undisk-mcp/setup-claude / stdio-proxy users, set --endpoint (or UNDISK_ENDPOINT) to either the base URL or a full MCP URL:
discover_tools_and_capabilities response includes the current workspace ID, current server time, provider capability notes, deployment metadata, and caller identity details.
Recommended routing strategy
- Use separate API keys per environment when possible.
- Include explicit workspace context in automation logs.
- Avoid implicit fallback behavior for production write paths.
Production checklist
- Verify workspace selection in both HTTP and WebSocket clients.
- Confirm your agent framework propagates auth headers exactly as configured.
- Add tests for workspace mismatch failures before broad rollout.
Error responses to assert in tests
Invalid workspace ID format
400.
Workspace-scoped key no longer valid
403.