Open Corvio
Corvio Help Center · MCP & agents

Connect Corvio MCP to Qwen Code

Qwen Code connects to the same Corvio remote MCP. The host opens Corvio's OAuth page, while Corvio continues to enforce Workspace membership, scopes, and document ACLs.

Updated 2026-09-09

Add Corvio in Qwen Code

Add Corvio as a remote HTTP MCP server in Qwen Code with the Corvio remote MCP URL.

Use https://api.corvio.ai/mcp. Do not paste an API key into the MCP URL, prompt, or configuration.

  1. Add a remote HTTP MCP or connector named Corvio.
  2. Use https://api.corvio.ai/mcp.
  3. Continue in the Corvio browser page and approve the requested scopes.
  4. Restart the Qwen Code session after authorization so it refreshes the available tools.
Qwen Code MCP documentation

OAuth is the normal sign-in

A normal interactive connection uses the Corvio authorization page. Sign in with any account method Corvio currently offers, review the requested scopes, and approve the request. The host exchanges the one-time authorization code itself.

CORVIO_API_KEY is an advanced Developer API or non-interactive CLI option. It is not required for remote MCP, must not be pasted into chat, and is not a fallback for a failed OAuth callback.

Verify the connection

Start with list_workspaces. Choose an authorized Workspace, then run search and fetch against a known document. A green OAuth page or a visible connector is only setup evidence; successful tool calls with the expected Corvio URLs prove the connection.

If authorization succeeds but the host still says authentication is required, remove the stale connection, start a new connection from the host, approve only the newest request, and begin a fresh session. Do not reuse an old authorization link.

  1. Run list_workspaces.
  2. Search for a known project or document.
  3. Fetch the result and check its Corvio URL.
  4. For write access, make one reversible test and read it back.

Turn a file into reusable work

A finalized upload preserves the exact original, hash, policy, and provenance; it does not by itself prove that Corvio interpreted or organized the file. A finalized UTF-8 Markdown Asset within the documented limit can become an editable Page through source_asset_id. For other formats or semantic restructuring, use organize_files or ask_corvio to create the Page, Spreadsheet, Presentation, Code, HTML Artifact, or reader layer that fits the job.

For a coherent source set, poll get_file_operation to terminal and inspect output_document, source_reconciliation, and skills_evaluation. Stable facts or preferences may enter Memory; only an evidence-backed reusable method, configuration, constraint, or quality bar becomes a Project Skill. skills_extraction_mode=always requires that decision and may validly return evaluated_no_qualifying_skill.

  1. Finalize the selected Asset and verify its ID and hash.
  2. Choose direct Markdown-to-Page conversion or a semantic organization/ask path.
  3. Poll to terminal and read the returned document or artifact.
  4. Keep the Skill candidate identity/resource receipt only when one qualified.

Delegate outcomes, then trust the receipt

For ask_corvio, pass the user's natural goal, complete decision-relevant context, and explicit constraints. Unless the user selected them, do not invent taxonomy, document titles, artifact counts, or Corvio's internal plan. Corvio decides the cognitive structure and carriers; related inputs may share a Project while independent reader jobs remain separate.

Poll get_question to a terminal state. Use artifact.url or links.primary_artifact exactly as returned: reader_output artifacts are user-facing results, structure_container artifacts are hierarchy, sources are evidence, and node_id is not a document URL.

  1. Send the natural outcome and complete context.
  2. Preserve user-specified constraints without adding new ones.
  3. Poll the Question to terminal.
  4. Return the canonical artifact URLs verbatim.