Add the remote server
Create a remote HTTP MCP entry named Corvio with https://api.corvio.ai/mcp. Preserve the URL exactly; do not add an API key to it and do not substitute a local callback address.
If the host supports Agent Skills separately, install the official Skill too. The Skill affects when the Agent uses Corvio; it does not grant access by itself.
Complete OAuth
The client should discover Corvio's protected-resource and authorization-server metadata, open a browser, and exchange the returned single-use code. Corvio never needs the user's password inside the MCP client.
If the client cannot perform OAuth for remote MCP, it is not currently compatible with Corvio's interactive connector flow. Do not work around that limitation by pasting a long-lived key into a prompt.
Verify capabilities and limits
Run list_workspaces, search, and fetch. Then verify one authorized durable action and read it back if the client will write. Remote MCP cannot inspect arbitrary local paths; use a client-supported selected-file upload or the optional local CLI for local bytes.
- Confirm the transport connects.
- Confirm OAuth completes in the client.
- Confirm authorized Workspace reads.
- Confirm any required write with current readback.