Help us improve
Share bugs, ideas, or general feedback.
From acp-agentic-commerce
Maps ACP checkout REST operations to MCP tools for AI agents to create, update, retrieve, complete, or cancel sessions via tool-calling in commerce servers.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin acp-agentic-commerceHow this skill is triggered — by the user, by Claude, or both
Slash command
/acp-agentic-commerce:acp-checkout-mcpThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Fetch live docs**:
Implements UCP Checkout as 5 MCP tools (create/get/update/complete/cancel) for AI agents. Guides building commerce MCP servers or Shopify integration.
Implements ACP REST checkout API: create, update, retrieve, complete, cancel sessions with state machine, data models, and headers. For merchant endpoints and AI agent flows.
Implements AP2 MCP servers to expose payment tools via Model Context Protocol for AI agent access. Use for building MCP-based AP2 payment integrations.
Share bugs, ideas, or general feedback.
Fetch live docs:
acp agentic commerce protocol MCP server implementation for MCP binding guidancehttps://developers.openai.com/commerce/specs/checkout/ for checkout operation semanticssite:github.com agentic-commerce-protocol MCP for any official MCP examplessite:github.com modelcontextprotocol python-sdk or typescript-sdk for current SDKACP's REST checkout operations can be exposed as MCP tools via an MCP server. This allows AI agents that use tool-calling (Claude, ChatGPT, Gemini) to invoke checkout operations directly as tools rather than making raw HTTP calls.
Each REST checkout operation becomes an MCP tool:
| REST Operation | MCP Tool Name | Description |
|---|---|---|
| POST /checkout_sessions | create_checkout_session | Create a new checkout session with items |
| POST /checkout_sessions/{id} | update_checkout_session | Update session (items, address, fulfillment) |
| GET /checkout_sessions/{id} | get_checkout_session | Retrieve current session state |
| POST /checkout_sessions/{id}/complete | complete_checkout_session | Submit payment to finalize |
| POST /checkout_sessions/{id}/cancel | cancel_checkout_session | Cancel the session |
Each MCP tool accepts JSON input matching the corresponding REST request body. The tool's inputSchema should be derived from the ACP OpenAPI spec's request schemas.
Each tool returns the CheckoutSession object (or error) as JSON, matching the REST response body.
AI Agent (Claude/ChatGPT)
↓ tool call (JSON-RPC)
MCP Server (your code)
↓ business logic
Checkout Service (same logic as REST)
↓ payment
PSP (Stripe)
The MCP server wraps the same business logic that the REST endpoints use. The checkout service layer should be shared between REST and MCP bindings.
idempotency_key as a tool parameterapi_version as a tool parameter or server configurationtype/code/message structureFetch the latest ACP OpenAPI spec and MCP SDK documentation for exact schemas and server setup before implementing.