API and MCP
Drive Opulent programmatically, and extend what a run can reach with MCP servers.
Programmatic session control
The API can create, search, inspect, message, wait for, stop, and archive sessions. The same control layer can manage automations, schedules, Knowledge, Skills, integrations, and security sweeps when the account has the required permission.
Programmatic control fits repeatable operations: a run started by your own product, a queue drained on your schedule, a workflow that belongs inside a system you already operate rather than beside it.
MCP servers
MCP servers add specialized tools: monitoring systems, databases, design tools, and internal services. Programmatic controls can list native integrations and MCP servers, show connection status, and return setup links.
Grant the smallest set the task requires. A recurring automation should carry an explicit tool allowlist rather than every connection available to the organization.
Repository tools
Repository tools can list available repositories, generate a structured wiki, read documentation topics, and answer grounded questions about the code. That is often the fastest way to give a run real context about a codebase nobody on the current team wrote.