Use case · Channels and architecture
Agentic commerce tools.
34 tools, 5 apps, 14 MCP servers and 15 shopping agents, assigned to this use case by a written definition. 31 of them are built mainly for this job. Filter by type, the platforms they work with and pricing.
- tools listed
- 34
- built mainly for this job
- 31
- apps
- 5
- MCP servers
- 14
- shopping agents
- 15
Active filters
3 tools match your filters
Showing 1 to 3 of 3, ordered by main purpose first
How results are ordered
Tools whose main purpose is this job come first, then tools where it is a documented feature. Alphabetical within each. This is not a ranking of quality.
There are no paid placements on use-case pages, and no ratings.
MnemoPay
MCP serverby MnemoPay (Jeremiah Omiagbo, J&B Enterprise LLC)
TypeScript SDK and MCP server for AI agent payments, giving clients tools for memory, wallet balance, charges, settlements, refunds and agent reputation scoring.
Main purposeSDK and MCP server providing escrow-backed payment rails and reputation scoring for agent-initiated purchases.
Stripe
- Runs
- Local · stdio
- Auth
- API key
- Maintainer
- Third-party company
Stripe ACP
MCP serverby CodeSpar
MCP server for Stripe and the Agentic Commerce Protocol, with tools for agent checkout sessions, customers, products, invoices, subscriptions and refunds.
Main purposeImplements Stripe's Agentic Commerce Protocol with MCP tools for agent checkout sessions, catalogue retrieval and delegated payment.
- Runs
- Local · stdio
- Auth
- API key
- Maintainer
- Third-party company
Stripe AI (Stripe MCP)
MCP serverby Stripe
Stripe's official repo offering a hosted MCP server at mcp.stripe.com plus agent plugins and skills for working with Stripe payments and billing.
Main purposeOfficial Stripe MCP server and toolkits let AI agents create payment links, invoices and refunds, providing agent payment rails with documented agentic commerce sample flows.
- Runs
- Local or hosted · HTTP, stdio
- Auth
- OAuth, API key
- Maintainer
- Official
From the ecommerceguide dataset
Agentic commerce tools in numbers
Calculated from all 34 tools on this page's list. Percentages are of the group named.
Further reading
- What's Agentic Commerce? The End of the Traditional Search JourneyAgentic commerce breaks the search-and-click loop. How autonomous AI agents handle discovery, evaluation, and transactions, and what the ACP protocol means for merchants.
- Agentic Commerce Protocols: How the Competing Standards DifferAgentic commerce protocols differ on who holds the payment credential and who owns the order. Compare the four axes, and see which commitments reverse.
- Agentic Commerce Is Not Solved: Where It Still BreaksThe real agentic commerce limitations: returns, disputes, order accuracy and no settled protocol. What a merchant can fix now, and what is still a bet.
How tools are assigned to a use case
What this page includes
Lets AI agents discover, compare or buy products, or helps merchants sell to AI agents: agent checkout and payment protocols and rails, agent-ready product catalogues and feeds, AI shopping agents that search or buy across merchants, and MCP servers whose documented tools let an agent search a catalogue, build a cart or check out as a buyer.
Not included: AI-visibility and AI search monitoring tools: tools that track, audit or improve how a brand, its products or its content are mentioned, cited or ranked in ChatGPT, Perplexity, Google AI Overviews, Gemini or other AI answers (GEO and AEO tools). A tool with such a feature qualifies only through a separate documented agent checkout, payment rail or agent-readable catalogue or feed. Store-admin MCP servers that manage products, orders or settings for the merchant. ERP, accounting, analytics or CMS connectors. General AI agent builders or chatbots with no commerce transaction.
How the assignment is made
Each use case has a written definition of what qualifies and what does not. A language model (Claude) reads each tool's listing, its summary and, for MCP servers, the verified integrations and tasks, and assigns it only where the definition fits. It sees no earlier assignments. 670 tools were classified, most recently in Sept 2026.
Main purpose or a feature
“Main purpose” means doing this job is what the tool is for. “A documented feature” means a named feature does the job but the tool's main purpose is something else. Anything weaker is left out. A tool can appear in at most three use cases.
What has to be true first
A tool appears here only once it is listed in its own section: MCP servers after their repository or documentation is verified, apps after their site and listing are reviewed. A use case gets its own page only with at least 10 such tools.
What the facts show
For apps, the pricing model and free plan or trial as recorded from the app's pricing page. For MCP servers, how they run, how they authenticate and who maintains them. “Works with” for apps comes from the listing's own text and is not a tested integration.
Order and corrections
Main-purpose tools first, then alphabetical. No paid placements and no ratings. Corrections: hello@ecommerceguide.com.