Linux 软件免费装
Banner图

Uncap AI Shopping Connector for WooCommerce

开发者 rantebi
更新时间 2026年10月5日 23:04
PHP版本: 8.0 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce ai agents mcp ucp acp

下载

1.0.0 1.1.0

详情介绍:

Uncap AI Shopping Connector for WooCommerce connects your store to AI shopping agents. It implements the Universal Commerce Protocol (UCP), ACP pre-flight discovery, and Model Context Protocol (MCP) tools. UCP and MCP agents can search products and create checkouts; ACP agents can detect the store and its currently advertised capabilities before attempting a transaction. What this means in practice AI agents like Claude, ChatGPT, and others are beginning to shop on behalf of users. When a user says "order me roses for my wife's birthday," the agent needs a structured way to find a store, check availability, and complete a purchase. UCP is the protocol that makes that possible. This plugin makes your WooCommerce store a first-class destination for those agents. Features Requirements

安装:

  1. Upload the plugin folder to /wp-content/plugins/
  2. Activate the plugin through the Plugins menu in WordPress
  3. Ensure WooCommerce is installed and active
  4. Go to Agentic Commerce → Dashboard for a store status overview
  5. Check Agentic Commerce → Settings for your live UCP, MCP, and well-known endpoint URLs

屏幕截图:

  • Products — per-product readiness scoring for what agents actually read
  • Checkouts — example agent traffic by protocol and funnel conversion
  • Settings — live endpoint URLs for UCP, MCP, and well-known discovery

常见问题:

What is UCP?

Universal Commerce Protocol (UCP) is an open standard that enables AI agents to interact with online stores. It defines how agents discover stores, browse product catalogs, create checkouts, and handle fulfillment. See ucp.dev for the full specification.

What is MCP?

Model Context Protocol (MCP) is a JSON-RPC 2.0 protocol that lets AI models call tools on external servers. This plugin exposes your WooCommerce store as a set of MCP tools, making it usable by agents like Claude Desktop without any custom code.

What is ACP support in this release?

Agentic Commerce Protocol (ACP) agents can use the public /.well-known/acp.json pre-flight document to detect the store, protocol version, currency, locale, and currently supported services. ACP checkout is not advertised or implemented yet; UCP and MCP remain the transaction-capable surfaces.

Do I need to change anything about my store?

No. The plugin works with your existing WooCommerce setup — products, payment gateways, shipping methods, and order flows stay exactly as they are. The plugin adds a protocol layer on top.

Which AI agents does this work with?

Any agent that implements UCP or MCP. That includes Claude (via MCP), and any custom agent built on top of the UCP open standard. The protocol is designed to be agent-agnostic.

Does this replace my normal WooCommerce checkout?

No. Human customers continue to use your regular WooCommerce checkout. The UCP/MCP endpoints are an additional interface used only by AI agents.

Why are some REST endpoints public?

UCP, ACP pre-flight discovery, and MCP discovery/search endpoints are public so agents can inspect public protocol capabilities and catalog data before checkout. OAuth authorize/token endpoints are public protocol entry points: authorization requires a logged-in WordPress user and nonce-protected consent, while token exchange requires a one-time authorization code or refresh token stored server-side. Checkout/order follow-up routes use generated checkout UUIDs rather than sequential WooCommerce order IDs, so possession of the active checkout UUID is the protocol credential for that session.

What data is sent externally?

By default, nothing. If the store owner enables Agent Webhooks under Agentic Commerce → Settings, the plugin may fetch the agent profile URL supplied in the UCP-Agent request header to discover a webhook URL, then POST order status events to that webhook URL at checkout time. URLs under https://ucp.dev/ and https://agenticcommerce.dev/ appear only as passive protocol/specification identifiers in discovery response payloads; the plugin never fetches them and never sends data to those domains. See the External Services section below for full details.

更新日志:

1.1.0 1.0.0