Skip to content

An MCP ecommerce surface connected to a real storefront.

Aly exposes agent-facing commerce resources without replacing the human storefront. MCP, REST, manifests, product pages, and checkout all point at the same store.

Aly mobile storefront interface
MCP + storefront
Agent tools and human pages share one source of truth.Discovery, catalog, cart, checkout, and policies stay explicit.

MCP belongs beside the catalog, not away from it.

98

Agent protocol coverage

Tools and pages
  • MCPEndpoint
  • CatalogREST
  • Checkoutx402

Expose tools without scraping

Agents can use explicit commerce resources instead of guessing from rendered product pages.

Keep the human web intact

Aly still serves normal pages, checkout flows, custom domains, and SEO surfaces for people.

Connect discovery to action

MCP, UCP, A2A, REST, and x402 routes form a chain from discovery to catalog inspection to transaction.

Agent tools, storefront APIs, and checkout share one store.

Aly storefront preview with commerce modules

Protocol-backed commerce Aly keeps the MCP endpoint tied to storefront products, policies, carts, checkout routes, and human-readable pages so agents and buyers see the same business.

Expose MCP tools and API resources as structured commerce actions.

Keep pages, checkout, payments, and fulfillment as the canonical store.

Watch the storefront system open up.

Aly starts as a public store for people, then exposes the same catalog, checkout, and discovery structure to agents without splitting the business into separate surfaces.

MCP ecommerce questions

Does Aly expose an MCP endpoint?

Yes. Aly exposes an MCP endpoint for API-key and OAuth-based agent use; browser session JWTs are not accepted for MCP.

Is MCP the only agent commerce protocol Aly supports?

No. Aly also exposes UCP, A2A, x402, REST storefront APIs, and discovery manifests alongside normal pages.

Do customers still use normal checkout?

Yes. Aly storefronts remain human-readable ecommerce sites with product pages, carts, checkout, and custom domains.

MCP for ecommerce only works when the store is authoritative.

Agents need explicit product, policy, cart, and checkout resources to transact safely.

Agent requirement

An MCP server should not be a disconnected wrapper around stale commerce data. Aly ties agent tools to the same storefront and checkout surfaces that buyers use.

Aly MCP commerce model

Open MCP endpoint
MCPtoolsRESTcatalogx402payments
Operators need one store record, not a separate protocol mirror to babysit.

Operator requirement

More public pages generated from the same commerce surface.

Connect agent tools to the storefront that already sells.

Build with Aly