ACP Checkout — MCP Binding

What it does

Describes how to implement an MCP server that exposes ACP/checkout REST endpoints as MCP tools. Each checkout REST operation (create, update, get, complete, cancel) becomes a tool with JSON input/output so agentic assistants can perform purchases or manage sessions via tool-calls. The document emphasises idempotency, schema derivation from ACP OpenAPI, error handling, and shared business logic between REST and MCP bindings.

When to use it

Use when building agent-facing commerce functionality where AI agents (Claude, Gemini, agentic platforms) should call checkout tools rather than raw HTTP. Suitable for prototypes and production integrations that want agent tool-calling for checkout flows.

What's included

• Scripts: none detected (has_scripts=false)
• References: recommends fetching ACP OpenAPI and MCP SDK docs (has_references=false in repo payload)
• Instructions: mapping REST operations to MCP tool names, recommended input/output schema treatment, idempotency and API-versioning guidance, and best practices for testing with an MCP inspector.

Compatible agents

Intended for agentic commerce frameworks and tool-capable assistants (Claude Code/Claude, Gemini CLI, agentic frameworks that support MCP tool-calling).