Community
free
Open code under the GNU AGPLv3. Run it for yourself, change it, contribute. If you let people use a modified version over a network, you publish your changes.
get the sourceOpen-source orchestrator with GOAP for tiny models. A chatbot for your website that works through your site’s own MCP / WebMCP tools — no GPU, no big model.
Early stage · in active development
Through MCP, an AI agent can use a product the way a person does: put an item in the cart, buy it, create a deal, log a call. This is how the big platforms got there.
Agents connect to any MCP-compliant server without custom code. A CRM stops being only a database and becomes something an agent works inside.
OpenAI and Stripe open-source the Agentic Commerce Protocol so an agent can buy inside the chat — US only, starting with Etsy. By March 2026 OpenAI moves checkout to retailers’ own apps: few merchants joined and the buy button converted under 1%.
Anthropic donates the protocol to the Agentic AI Foundation, co-founded with Block and OpenAI and backed by Google, Microsoft, AWS and Cloudflare. Supported by ChatGPT, Gemini, Copilot, Cursor and VS Code.
The Storefront MCP server lets an agent search the catalog, read product details and store policies, build and edit a cart, and hand the shopper a checkout link. Shopify now steers new integrations to its Universal Commerce Protocol endpoint.
Read and write access over OAuth 2.1: contacts, companies, deals, tickets, plus calls, meetings, notes and tasks. Every action respects the user’s own permissions.
A Salesforce-managed endpoint exposes an org’s data, flows, Apex actions and queries to any MCP-compatible client, Enterprise Edition and above.
PleiadesOrchestra is a self-hosted orchestrator for tiny models. Instead of one huge prompt it builds a chain of actions towards a goal (GOAP), so a 1B-parameter model can find a product, add it to the cart or compare items on a real site. It works with facts and prepared answers — it does not pretend to be a professional consultant.
Two different transports, not one catalog reachable two ways. Pleiades supports both.
WebMCP is experimental. It is a W3C Community Group draft, shipped in Chrome as an early preview and not yet a stable cross-browser feature. The API surface is still changing: the draft moves from navigator.modelContext to document.modelContext. Chrome Status lists Chrome 157, due 3 November 2026, as the anticipated release — a target, not a committed date. source, release target
| MCP server | WebMCP (experimental) | |
|---|---|---|
| where the tools live | On an MCP server the orchestrator can reach (stdio / SSE). | In the visitor’s browser, on the page that embeds the widget (navigator.modelContext). |
| who runs the call | The server calls the tool itself. | The widget calls it in the browser; the server pauses the plan and resumes it with the result. |
| what the site needs | A real MCP server next to the shop or service. | Only the tools it already exposes on its pages — no backend integration. |
| sees the visitor’s state | Only what the server knows. | Yes: the open page, the cart, the chosen city — as the visitor sees it. |
| maturity | Established protocol. | Experimental browser API; behind a flag in Chrome today. |
Most small shops run on WooCommerce, OpenCart or 1C-Bitrix, not on Shopify. None of them gives a ready shopping agent out of the box. Pleiades is a widget on the page, so it does not wait for the CMS to become agent-ready.
WordPress has an official MCP Adapter, and WooCommerce ships an MCP integration since 10.3. Both are still early: WooCommerce calls it a developer preview.
sourceThe most used store engine in Russia (about 29% of shops, though over half run a custom CMS). Bitrix24 has official MCP servers; for the store engine we found only third-party developer tools.
sourceA separate store CMS, not a WordPress plugin. No official MCP; third-party extensions exist, such as EcomAiBridge in the OpenCart marketplace.
sourceBuilt for small businesses without a GPU or a budget for expensive models.
GOAP builds a chain of actions towards the goal, so a small model stays on track.
Find a product, add to cart, compare — through the MCP / WebMCP tools you already have.
The whole stack runs on one Linux machine with Docker Compose. Your data stays yours.
One web component, under 40 kB brotli, works in React, Vue, Svelte or plain HTML.
The admin panel draws each request as a graph: prompt, steps, tool answers, result.
Whoever owns the agent owns the recommendation, the ad and the customer. That is the real question behind every protocol on this page.
Its Commerce Protocol is closed and proprietary, not MCP. A closed platform that ranks the recommendations in the dialogue and sells the ads around them has every reason to favour its own results. The shop becomes a supplier; the customer relationship and the ad budget go to the platform.
sourceWebMCP and the Universal Commerce Protocol are open — and they feed Google’s own search, ads and Merchant Center. The more sites expose tools in the open, the more of the traffic is automated: corporate agents and bots of every kind that the shop does not control.
sourceBrowser vendors are not aligned: Mozilla has filed concerns about agents acting without the user seeing it, and WebKit opposes sites telling agents from people. Limits, permissions and an audit trail belong on the shop’s side.
sourcePleiades is self-hosted. Recommendations, customer data and the ad slot stay on the shop’s own site instead of moving into someone else’s results. The plan behind every answer is a readable graph, and the tools are the ones the site itself exposes.
free
Open code under the GNU AGPLv3. Run it for yourself, change it, contribute. If you let people use a modified version over a network, you publish your changes.
get the source500$ one time
Private code: build it into a closed-source product or run a modified version without publishing it. Perpetual license, covers all versions. No support included.