Connect your commerce to Muse

Connect your catalogue to Muse with an MCP connector and PAP (Personal Agent Protocol, also called Poppy). Add your MCP App experience where the host supports it.

Muse connector · MCP App · PAP (Poppy)

From conversation to commerce

A shopper gives Muse a shopping task → your connector supplies product information → Muse uses the available tools → the shopper follows the supported buying journey.

A connector for shopping tasks


Give Muse a documented way to find products and interact with your commerce service. CartmelAI helps structure the MCP tools, inputs and outputs around your catalogue, with clear read and write permissions and explicit handling of sensitive actions.


Prepare your MCP App experience


Reuse an interactive commerce experience built around product discovery, details and contextual actions. We help prepare the MCP App and validate what Muse’s current host can render before choosing the final interface and handoff.


Keep commerce actions explicit


Separate reading product information from changing a basket or starting a transaction. CartmelAI helps define account access, confirmation points and error responses, so supported actions follow the merchant’s rules and the platform’s requirements.


From integration to review


Prepare tool documentation, authentication details, test access and representative shopper scenarios for connector review. CartmelAI helps validate the submitted journey and monitor the integration once the relevant access is available.


PAP: connect the personal agent journey

CartmelAI supports PAP (Personal Agent Protocol), also known as Poppy, for personal-agent journeys such as Muse. It connects company discovery, agent identity, authorized account access and continuity across website, API and company-agent interactions. We help configure the merchant capabilities and permissions needed for your journey.

Plan your launch with CartmelAI

Muse connector approval and availability follow Meta’s requirements. Interactive MCP App rendering must be validated in the target host; an MCP connection alone does not establish UI support.