Mcp

Shopify CRO platform via MCP: 100+ tools for analytics, experiments, authoring, proven lift.

ai.eevy/mcp is a Shopify conversion rate optimization platform delivered as an MCP server. The publisher, ai.eevy, exposes more than one hundred tools through this server, grouped around analytics, experiments, authoring, and what the upstream record describes as proven lift. An agent that connects to this server can query Shopify performance data, manage tests, and edit storefront content, because the available tool categories explicitly cover analytics, experiments, and authoring. The server advertises a large surface area of over one hundred capabilities, though the registry record does not enumerate individual tool names or schemas. Communication happens over streamable HTTP, so the host client must support that transport rather than stdio or SSE. There is no package identifier, version, installation command, or repository URL listed in the facts, and no license is declared. The capability is specifically scoped to Shopify; it is not presented as a general e-commerce or multi-platform solution. Because the tools span reading data, testing changes, and writing content, an agent could theoretically execute a full CRO workflow from a single connection without handing off to other integrations, provided the host handles streamable HTTP.

Use cases

  • use it to read Shopify analytics through an agent
  • use it to create and manage experiments on a Shopify store
  • use it to author and edit store content via MCP tools
  • use it to run conversion rate optimization workflows from a single server
  • use it to orchestrate CRO tasks when the host supports streamable HTTP

When to use it

  • when your agent needs to interact with Shopify for CRO tasks
  • when your MCP client supports streamable HTTP transport
  • when you want analytics, experiments, and authoring in one integration

When not to use it

  • when you need a local stdio transport instead of streamable HTTP
  • when you are not working with a Shopify store
  • when you require documented tool schemas or explicit package installation steps