MCP
DirectionConnect Continual and external agents to a project through one discoverable interface.
Each project can expose its backend through a project-scoped MCP server. The Continual agent and authorized external agents discover the same company context and governed capabilities without a custom integration for every client.
What MCP exposes
ToolsTyped actions the current actor may request.
ResourcesDiscoverable project context and metadata suitable for reading.
Platform servicesNarrow project capabilities such as work items or source changes, when explicitly published.
Identity and scope
A connection identifies the user or delegated agent and the project it is entering. Discovery is permission-scoped: the client sees only the capabilities available to that identity. Tool calls still pass through backend authorization and human-review policy.
What MCP does not do
- It does not replace the backend's business rules.
- It does not bypass identity, authorization, or approval.
- It does not make chat history the system of record.
- It does not replace the HTTP API used by ordinary apps.