Eevy

ai.eevyPublished by eevy.aiOfficial publisherv1.0.1Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Eevy is a remote MCP server for a Shopify conversion-rate-optimization platform, exposing 100+ tools for analytics, experiments and authoring.

What you can do
  • Read analytics and performance data from the Shopify CRO platform
  • Run and inspect experiments, including proven lift results
  • Author and manage CRO content and changes through the platform's tools
  • Work with the platform's 100+ tools from an assistant over a single remote connection
When to use it
Useful when you run a Shopify store and want an assistant to pull CRO analytics, check experiment results, or draft and manage optimization work inside the Eevy platform instead of switching to its web interface.
Requirements
A remote MCP endpoint at mcp.eevy.ai over streamable HTTP; OAuth authentication is required, so an Eevy account with access to the relevant store is needed. No packages, environment variables or headers are declared.
Before you install
Access is granted through OAuth to a live Shopify CRO account, so the assistant may be able to change experiments and authored content, not just read them. Review what the granted scopes allow before connecting, and confirm which actions write to the store.

Installation

In SourceWeft

  1. Open Eevy in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.eevy%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "eevy": {
      "type": "http",
      "url": "https://mcp.eevy.ai/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.