Build and operate Rylvo through MCP
Connect compatible AI editors to a broad workspace tool surface for bots, knowledge, prompts, guardrails, and operations.
MCP Hub lets a compatible editor or assistant work with Rylvo through the Model Context Protocol. Instead of managing every resource in isolation, teams can inspect a workspace, describe the change they want, and use the available tools to carry it out.
A connected workspace surface
The tool catalog spans bot setup, prompts, knowledge bases, skills, guardrails, connectors, and operational resources. Read tools help an assistant understand the current state; write tools let it create or update resources within the caller's permissions.
Governed actions
Tool calls follow workspace authorization, resource quotas, and audit logging. Actions with greater impact are classified for approval so operators can review what will happen before it executes. The same MCP surface powers Workspace Architect in the dashboard, keeping the experience consistent across Rylvo and external editors.
MCP Hub gives teams a flexible interface for building repeatable workspace setups while retaining visibility into what changed.