Add one remote endpoint
Open the host's current MCP, Tool Provider, or Plugin settings and add https://api.corvio.ai/mcp as a remote HTTP server. Choose OAuth when offered; never paste a Corvio API key into a prompt, project file, or shared configuration.
After authorization, start a fresh Agent session when the host snapshots tools. Call list_workspaces first and pass one explicit Workspace ID to later calls.
- Open the host's remote MCP settings.
- Add the Corvio endpoint and complete OAuth.
- Reload tools or start a new Agent session.
- Verify list_workspaces, search, and fetch.
China-focused hosts
For Qwen Code, Kimi Code, and TRAE, use the host's current remote MCP or extension surface and the same Corvio URL. For Dify, add Corvio as a remote MCP tool provider and re-publish the workflow or Agent when Dify requires it.
Package formats and marketplace availability differ. A working direct MCP configuration does not prove that a Corvio listing has passed Qwen, Kimi, TRAE, Dify, or another host's review.
Verify without widening access
A complete receipt is: OAuth completed, list_workspaces returned only current memberships, search returned the expected title and URL, and fetch returned the current body under the same ACL. Removing membership or revoking the generated Corvio API key must remove later access.
Remote MCP cannot scan local files. If a host does not support remote HTTP MCP, use the reviewed Corvio Skill and local CLI, or export files manually; do not switch to shared secrets or arbitrary Home-directory crawling.