Developers · AAES Operate · MCP

Operate MCP.

An independent product interface planned with its own permissions and versioned contract.

This documentation describes AAES Operate. Operational controls and private-work permissions are independent of AAES Govern policy and evidence. About AAES Operate

Under implementation

A separate Operate MCP surface is being implemented with the same operation and permission boundaries as the Operate developer API.

The existing Govern MCP adapter is a different resource. Connecting an agent to that adapter does not grant access to private Operate projects or tasks. A tested client and transport matrix will accompany the supported Operate release.

Evaluate the current product

Operate supports private projects and tasks, corporate OIDC identity and explicitly configured HTTP agents in the supported evaluation profile. Deployment and workload integration guides ship with the evaluation package. Current role and resource membership control access independently of Govern.

Read the current Operate integration scope and prepare a scoped evaluation.

Using Govern and Operate together

Adding Govern does not replace Operate permissions. Each product remains responsible for its own identity, authorization and records. The shared workspace is under implementation; current UI and deployment acceptance must be agreed for the exact release.

Read the combined integration boundary or compare the current Govern MCP contract.