Module reference

UCP Checkout over MCP for Magento 2 — module reference

Covers angeo/module-ucp-checkout-mcp 1.0.0 · Checked 16 October 2026 · MIT licensed

UCP Checkout over MCP offers the UCP checkout for agents that speak MCP instead of REST. It adds five tools to the store MCP server from MCP Server, following UCP spec 2026-08-25 (MCP binding).

All the logic lives in UCP Checkout. REST and MCP give the same results and share sessions. An agent can even mix them.

Tools

ToolWhat it does
create_checkoutNew checkout from items, buyer, address and discount code
get_checkoutCurrent state, shipping options, and the order once paid
update_checkoutFull replacement of items, buyer, discount and shipping
complete_checkoutHandoff: requires_escalation + continue_url. The buyer pays on your checkout.
cancel_checkoutCancel an open checkout

Arguments

{
  "meta": {
    "ucp-agent": { "profile": "https://platform.example/profile" },
    "idempotency-key": "550e8400-e29b-41d4-a716-446655440000"
  },
  "id": "chk_…",
  "checkout": { "line_items": [{ "item": { "id": "24-MB02" }, "quantity": 1 }] }
}

meta["ucp-agent"].profile is required. idempotency-key works like the REST header: the same key and body give the same answer; the same key with another body gives a tool error.

Requirements

Magento2.4.6+ (Open Source, Mage-OS or Adobe Commerce) — magento/framework >=103.0.6 <104
PHP8.1 – 8.5 — ~8.1.0||~8.2.0||~8.3.0||~8.4.0||~8.5.0
Other angeo modulesangeo/module-ucp ^2.2
angeo/module-ucp-checkout ^1.1
angeo/module-mcp-server ^2.2.2
PHP extensionsjson

Installation

composer require angeo/module-ucp-checkout-mcp
bin/magento module:enable Angeo_UcpCheckoutMcp
bin/magento setup:upgrade
bin/magento setup:di:compile                # production mode only
bin/magento cache:flush

Then set Stores → Configuration → Angeo → UCP (Universal Commerce Protocol) → Transport → MCP Endpoint URL to https://your-store/mcp, so the profile advertises the MCP transport next to REST. Check the tools with:

bin/magento angeo:mcp:tools

This module has no settings of its own. Session lifetime, limits and legal links come from UCP Checkout.

FAQ

Do I need UCP Checkout as well?

Yes. This module is a thin MCP layer. All checkout logic, limits and sessions come from UCP Checkout.

Is it different from MCP Checkout?

Yes. MCP Checkout places guest orders with server-side limits and pay-by-link. This module follows the UCP checkout model, where the buyer always pays on your own checkout through continue_url.

Can an agent switch between REST and MCP?

Yes. Both share the same sessions, so a checkout created over REST can be read or completed over MCP.

How does the profile show the MCP transport?

Set the MCP Endpoint URL in the UCP Profile transport settings to your store’s /mcp address. The profile then lists MCP next to REST.

This page was written from the README.md, composer.json and etc/*.xml files of tag 1.0.0, read on 16 October 2026. Settings, commands and defaults come straight from that code. If a newer release is out, the README on GitHub wins.