New Release|We just open-sourced 8 agentic commerce plugins for Claude CodeExplore the plugins

We just open-sourced 8 agentic commerce plugins for Claude Code

Β·

We just open-sourced 8 agentic commerce plugins for Claude Code

Build agent-ready commerce directly from your terminal.

Today we're releasing agentic-commerce-claude-plugins, a collection of 8 open source plugins that bring agentic commerce expertise into Claude Code. MIT licensed. Free to use, modify, and distribute.

Why plugins for agentic commerce?

Agentic commerce is moving fast. New protocols are shipping. New platform APIs are launching. And developers building agent-ready storefronts are spending too much time reading specs and debugging protocol compliance by hand.

Claude Code plugins solve this by encoding domain expertise directly into your development workflow. Instead of switching between protocol docs and your editor, you get a coding assistant that already knows the specs, the patterns, and the pitfalls.

Without plugins vs. with plugins

Building agent commerce today

Read protocol specs

Hundreds of pages across UCP, ACP, MCP, A2A, and WebMCP

Translate to code

Manually implement endpoints, schemas, and validation

Debug compliance

Discover issues in production through lost transactions

Repeat for each protocol

Each protocol has different patterns and pitfalls

Building with Claude plugins

Ask Claude

Protocol expertise is built into your coding assistant

Generate conformant code

Endpoints, schemas, and validation out of the box

Catch issues in development

Automated hooks check compliance as you code

Works across all protocols

One plugin per protocol, consistent workflow

Less time reading specs. More time building.

What's in the box

The collection includes 5 protocol plugins and 3 platform plugins:

Protocol plugins

UCP (Universal Commerce Protocol) gives Claude deep knowledge of the Google/Shopify standard for structured product search, cart management, checkout, and payment. Generate conformant endpoints, validate schemas, and catch idempotency issues before they reach production.

ACP (Agentic Commerce Protocol) covers the OpenAI/Stripe standard for multi-agent negotiation. Capability advertisement, delegation tokens, dialogue-based commerce, and context propagation across agent handoffs.

AP2 (Agent Payments Protocol) encodes Google's secure payment mandate system. Build and validate payment delegation chains, mandate lifecycle management, and consumer authorization flows.

A2A (Agent-to-Agent) handles multi-agent communication, task delegation, status notifications, and auth handshakes between agents operating across trust boundaries.

WebMCP (Web Model Context Protocol) covers browser-native agent APIs through web manifests, form annotations, and polyfilled tool invocations. The fastest path to making existing websites agent-accessible.

5 protocol plugins

πŸ“¦
UCPCommerce

Structured product search, cart, checkout, and payment. Google/Shopify standard.

🀝
ACPNegotiation

Multi-agent negotiation, delegation tokens, and dialogue-based commerce. OpenAI/Stripe standard.

πŸ’³
AP2Payments

Secure payment mandates, delegation chains, and consumer authorization. Google standard.

πŸ”„
A2ACoordination

Multi-agent task delegation, status notifications, and cross-boundary auth.

🌐
WebMCPWeb

Browser-native agent APIs through web manifests and form annotations.

Each plugin encodes the full protocol specification so Claude can generate, validate, and debug conformant code.

Platform plugins

Magento 2 brings full knowledge of Magento Open Source and Adobe Commerce APIs, catalog management, and integration patterns for agent-ready commerce.

BigCommerce covers the BigCommerce platform APIs, storefront integration, and agentic commerce setup.

WooCommerce includes WordPress commerce REST APIs, plugin architecture, and agent integration patterns.

3 platform plugins: coverage at a glance

100%
Magento 2 APIsPASS
100%
BigCommerce APIsPASS
100%
WooCommerce APIsPASS

Full API coverage for all three platforms. Catalog, cart, checkout, and agent integration patterns included.

What each plugin includes

Every plugin follows a consistent structure:

  • Agents with specialized knowledge for each protocol or platform
  • Skills for common tasks like generating endpoints, validating schemas, and debugging flows
  • Hooks for automated checks during development

What's inside each plugin

β†’
Agents with specialized protocol/platform knowledge
Agents
↑
Common tasks: generate endpoints, validate schemas, debug flows
+Skills
↑
Automated compliance checks during development
+Hooks
=
Full development toolkit for agentic commerce
Complete

Consistent structure across all 8 plugins.

Getting started

Clone the repo and install whichever plugins you need:

git clone https://github.com/OrcaQubits/agentic-commerce-claude-plugins.git
claude plugin add ./ucp-agentic-commerce

Then just ask Claude to help you build:

claude "Help me implement UCP checkout for my Shopify store"
claude "Validate my ACP capability advertisement endpoint"
claude "Generate A2A task coordination handlers"

From zero to agent-ready in three steps

Step 1Clone the repository

git clone https://github.com/OrcaQubits/agentic-commerce-claude-plugins.git

Step 2Install the plugins you need

claude plugin add ./ucp-agentic-commerce (repeat for each protocol or platform you use)

Step 3Start building with Claude

Ask Claude to generate endpoints, validate schemas, debug compliance, or simulate agent interactions.

Works with any existing codebase. No vendor lock-in.

Why open source

We believe the tooling layer for agentic commerce should be open. The protocols themselves are being developed in the open. The platforms are publishing their specs publicly. The testing and development tools should follow the same path.

Open sourcing these plugins means:

  • Faster adoption: developers can start building agent-ready commerce today, not after reading hundreds of pages of protocol specs
  • Community contributions: as protocols evolve, the community can help keep plugins current
  • Transparency: merchants and platforms can see exactly what expertise powers the tools they use

β€œThe protocols are being developed in the open. The platforms are publishing their specs publicly. The development tools should follow the same path.”

Open sourcing these plugins means faster adoption, community contributions as protocols evolve, and full transparency into what expertise powers your tools. We believe the tooling layer for agentic commerce should be as open as the protocols it supports.

What's next

This is the first release. We're planning to add more plugins as the agentic commerce ecosystem grows, including plugins for Shopify's agent APIs, Salesforce Commerce Cloud, and emerging payment protocols.

If you find a bug, want to add a feature, or have ideas for new plugins, open an issue or submit a PR. We'd love to build this together.


Check out the repo at github.com/OrcaQubits/agentic-commerce-claude-plugins. Star it if you find it useful.

Julekha Khatun : jkhatun@orcaqubits-ai.com

Rohit Bajaj : rbajaj@orcaqubits-ai.com