MCP catalog operations

Catalog operations bring the Cloud Management Platform (CMP) catalog into any MCP-compatible AI agent. Users can find, order, reorder, and approve catalog items in natural language. The agent resolves the blueprint, group, environment, and required parameters, then submits the order.

How it works

When a user requests something from the catalog, the agent handles the entire process:

1. It finds the matching blueprint from the blueprints the user is permitted to order.
2. It determines where the order can go, such as the valid groups and environments, choosing automatically when there is only one option and asking when there are several.
3. It resolves the required parameters, refreshes dependent options, and applies the same show/hide rules as the UI order form.
4. It presents the complete order for confirmation before submission.
5. It returns an order ID and tracks the order to completion.

For multi-tier blueprints that require environment selection, the agent first resolves the environment, then loads only that environment’s parameters. This ensures quick responses regardless of how many environments a blueprint spans.

Reordering from history

The agent can reconstruct a complete order from a user’s most recent previous order of the same blueprint. The reconstructed order is presented for confirmation and adjustment before submission. If the blueprint has changed since the original order, the user is informed.

Tracking and approvals

The agent can locate orders by status, group, or owner. For approvers, it surfaces only the orders the authenticated user is entitled to approve. Approvals or denials (with optional reason) can be submitted directly from a conversation. Orders placed through the agent follow the approval policy already defined by the blueprint and group.

Technical notes

Catalog operations reuse the same BlueprintService and order pipeline as the CMP web UI and v3 REST API, meaning:

• Any order that succeeds via the agent would also succeed in the UI under the same user, group, blueprint, and values, and failures produce the same errors.
• Discovery, group and environment resolution, submission, and approvals are all scoped to the authenticated user’s permissions.
• Show/hide rules, generated options, recipient rules, and quota all behave identically to the UI.