Add the remote endpoint
Open WorkBuddy's Connector, Tool, or MCP settings and add https://api.corvio.ai/mcp as a remote HTTP endpoint. Choose OAuth when the host offers it and complete the Corvio authorization screen.
If the installed WorkBuddy version does not support remote MCP, use the official Corvio Skill and local CLI instead of pasting API keys into prompts or documents.
- Open the host's MCP or Connector settings.
- Add the Corvio remote HTTP endpoint.
- Complete OAuth and review scopes.
- Start a fresh agent conversation if the host snapshots tools per session.
Select scope explicitly
Run list_workspaces and pass the chosen Workspace ID to search or ask_corvio. Corvio does not infer a Workspace from a title, and the connector cannot see a Workspace the connected account cannot view.
Begin with list_workspaces, search, and fetch. Enable broader agent use only after the returned title, excerpt, full body, and Corvio URL match the expected source.
Troubleshoot without widening access
A 401 response means the OAuth connection is missing or expired. A missing Workspace or document usually means current membership or document ACL does not allow it. Reconnect or ask the Workspace owner; do not switch to a shared secret.
WorkBuddy configuration changes over time. If the UI does not match this guide, search Corvio Product Guidance or WorkBuddy's current official help using the goal 'add a remote HTTP MCP', while preserving the same OAuth and ACL boundaries.