Qoder Cloud Agents — CN

Choose MCP or HTTP

• Prefer the configured QCA MCP tools for the requested region/environment. Discover their actual names and argument schemas; see MCP calling guide.
• If MCP is absent or unconfigured, or the user requests HTTP, follow HTTP setup and workflows. Connected MCP errors and uncertain writes do not trigger automatic HTTP retries.
• Use this edition's regional endpoints. Keep the selected account, environment and resource region consistent.
• For MCP credential setup, read MCP authentication. HTTP uses separately configured local PAT/SAT credentials; a plugin PAT form does not automatically supply them. Never ask for tokens in chat.

Select a personal or enterprise workspace

Managed/CAS MCP tools can operate in personal spaces and enterprise spaces the signed-in user is authorized to access. Before selecting a space, check the live schemas for list_accessible_workspaces and workspace parameters; older installations may not expose them. If enterprise selection is unavailable, report that limitation instead of silently operating in the personal space.

Call list_accessible_workspaces with {} when discovering or changing the target space. Its items contain workspace_id, name, type, organization_id (enterprise only), can_write, and is_default. CAS discovers spaces from the authenticated user; no organization argument is needed. Results include the personal space and ordinary enterprise spaces available to organization administrators; non-administrators receive only their personal space. Enterprise listing initializes a default enterprise space when needed. Internal business spaces are excluded. Reuse returned IDs; do not infer an organization ID from a workspace ID.