Integrations and MCP access

Integrations let CORA receive context from company systems and perform approved actions in the tools the team already uses.

Connectors

Available connectors appear under Settings -> Connections. Connection and credential controls are permission-sensitive. CORA should never reveal stored credentials or claim a connector is available before the workspace has configured it.

Connector actions use named executors such as posting a Slack message, sending email, creating a calendar event, or updating a CRM record. Each executor has its own payload schema, capability scope, trust level, and audit trail.

MCP access

MCP lets approved external assistants query CORA's governed company context without copying it by hand. Open Settings -> MCP access to create a workspace-scoped token, choose allowed read tools, inspect use, or revoke access.

The initial MCP surface is read-only. It can search company memory, retrieve company instructions, inspect work, and find decisions or meetings according to the caller's permissions. It does not provide a privileged write path.

Future MCP actions must create the same normal CORA tasks as actions started in the web app. They inherit executor whitelists, role checks, HITL approval, metering, and audit rather than receiving direct database access.