Fetch live spec: Web-search site:ucp.dev specification checkout-mcp and fetch the page for exact tool definitions, JSON-RPC envelope format, and _meta requirements.
For Shopify's production MCP server, fetch https://shopify.dev/docs/agents/checkout/mcp for auth flow and endpoint details.
UCP over MCP is a 1:1 mapping of checkout operations to MCP tools using JSON-RPC 2.0. The same data model as REST, different envelope.
| MCP Tool Name | Maps To | Key Inputs |
|---|---|---|
| --------------- | --------- | ------------ |
create_checkout | POST /checkout-sessions | checkout object + idempotency_key |
get_checkout | GET /checkout-sessions/{id} | id |
update_checkout | PUT /checkout-sessions/{id} | id + checkout object |
complete_checkout | POST .../complete | id + payment_data + idempotency_key |
cancel_checkout | POST .../cancel | id + idempotency_key |
Every MCP tool call MUST include _meta.ucp.profile pointing to the platform's UCP profile URI. This replaces the UCP-Agent HTTP header from the REST binding.
UCP errors embed inside JSON-RPC 2.0 error responses:
error.code: -32603 (Internal Error)error.data: Contains an errors[] array, where each error has code, message, severity, and details fieldsBuilding a Business MCP Server:
@modelcontextprotocol/sdk for Node, mcp for Python)_meta.ucp.profile from every tool call for negotiationConnecting to an existing MCP server (e.g., Shopify):
_meta.ucp.profile and checkout payloadsShopify provides a production MCP server for UCP checkout. Before implementing:
POST https://api.shopify.com/auth/access_token with client credentialsPOST https://{shop-domain}/api/ucp/mcp共 1 个版本