What is a #checkout MCP server?
An MCP server tagged #checkout implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access checkout-related tools, data, or APIs.
Every MCP server and client below is tagged #checkout — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to checkout tools.
Checkout Page
Create checkout pages, sell event tickets, manage customers, payments and subscriptions from your AI assistant.
Final Commerce
Build custom POS apps with your AI agent. Final's MCP server lets developers scaffold checkout flows, adapt vetted screen blueprints for counter POS, self-checkout kiosks, restaurant ordering and payment terminals, previ
SyncSpider-GmbH
B2Bware MCP server that connects MCP-compatible AI clients to the B2Bware Datahub API. Supports product search/listing, customer lookup, cart upsert with optional custom line-item pricing, robust order sorting (e.g. -id, -_created_at), and checkout with explicit shipping/billing
Flyger1an
Agentic-commerce MCP: search across merchants, fetch structured offer manifests, and dry-run checkout + negotiation before buying.
Getly-Store
Your AI assistant runs a real digital-products store: create & publish products (2GB file delivery included), write
themonagroup
MONA Pay for AI agents: create VietQR codes, check incoming bank transfers in real time, configure and test webhooks, verify HMAC signatures, send transactional email and Zalo notifications. Bank API and automatic paymen
Common questions about MCP servers and clients tagged #checkout
An MCP server tagged #checkout implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access checkout-related tools, data, or APIs.
mcp.so currently lists 6 MCP servers and clients tagged #checkout.
Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.