Open Corvio
Corvio Help Center · MCP & agents

Corvio MCP: install, connect, and verify

Corvio MCP gives an AI host permission-scoped access to the Workspace you authorize. Use the host's Connector or MCP surface for live tools, add the Corvio Skill or Plugin for proactive collaboration guidance, and use the CLI only when the host must work with local files or a project-bound Agent.

Updated 2026-09-09

Choose the right Corvio surface

Remote MCP is the live connection: add https://api.corvio.ai/mcp and sign in through Corvio OAuth. The Skill teaches the Agent when to retrieve shared context and when to return durable results. A Plugin can bundle both. The optional @corvio/cli is only for local paths, downloads, sync, or a project-bound Agent.

You do not need to create an API key for a normal Claude, ChatGPT, Codex, WorkBuddy, Cursor, or other interactive MCP connection. Never paste a credential into a chat prompt.

Download the standalone SkillDownload the Claude/Cowork PluginOfficial GitHub source

Install and authorize

Prefer a Corvio listing in your host's trusted directory when it is available. Otherwise add the remote HTTP MCP URL directly and complete the Corvio authorization page. In hosts with a separate Skills surface, install the Skill as well; in Claude Cowork or Claude Code, the Corvio Plugin bundles the Skill and MCP definition.

Sign in with any account method offered on the Corvio page, inspect the requested scopes, and approve. Corvio returns control to the host; the host—not the user—exchanges the single-use authorization code.

  1. Open the host's Connectors, MCP, or Plugins settings.
  2. Add https://api.corvio.ai/mcp or install the Corvio Plugin.
  3. Complete Corvio OAuth without changing the callback URL.
  4. Start a fresh host session.

Prove the full connection

Call list_workspaces, then search and fetch one known document. If the Agent will write, make a reversible edit or create a test document and read it back. An installed package, successful consent page, or visible tool list is not sufficient proof by itself.

For a file workflow, verify the whole value chain: finalized Asset, direct Markdown Page or appropriate derived representation, terminal organization receipt, source reconciliation, and any evidence-qualified Memory/Skill result. Upload alone is not completion, and an always Skill policy may correctly return evaluated_no_qualifying_skill.

If the host says authentication is required after Corvio approved the request, remove the stale host connection and start a new one. Authorization links and codes are single-use. If a cloud Agent cannot download the ZIP because of its network policy, download it in your browser and upload it through the host's Plugin or Skill UI instead.

  1. Verify list_workspaces.
  2. Verify search and fetch.
  3. Verify one authorized write and readback when needed.
  4. Keep a trivial or sensitive task as a countercase that should not be uploaded automatically.