# shopbuddy [Health: Active]

**Category:** 🛒 E-Commerce  
**Repository:** https://github.com/tmill313/shopbuddy-plugin  
**GitHub Stars:** 0  
**npm Downloads (last month):** 109  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/shopbuddy-2

## Description
Safe Shopify theme changes for AI agents: staging, validation, visual review, approval, rollback.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "shopbuddy": {
    "command": "npx",
    "args": ["-y","shopbuddy"]
  }
}
```

## Documentation

## What shopbuddy MCP server does

The shopbuddy MCP server provides an MCP interface for making controlled changes to Shopify themes. Instead of applying edits directly to the published theme, it starts from a duplicate staging theme and maintains a server-side working copy for the agent. This structure is intended for AI-assisted theme development where owners need to inspect changes before publication.

The repository is a public companion to the hosted Shop Buddy service. It contains the Claude Code plugin and marketplace metadata, the Shop Buddy skill, MCP client configuration, and the MCP Registry manifest. The service itself is hosted, while the local command-line package is distributed through npm.

## How it works

A change begins with `shopbuddy_start_change`, which duplicates the live theme into an unpublished staging theme and retrieves it into the working copy. The agent can then read, search, and write theme files. After editing, `shopbuddy_validate` runs Theme Check against the changes.

`shopbuddy_push_preview` uploads the working copy to staging and captures screenshots before and after the change on mobile and desktop. The preview includes a plain-language explanation of what changed, with visual changes attributed to their sections. This gives the store owner both code validation and a visual review step.

The agent can use `shopbuddy_submit` and `shopbuddy_request_publish` to provide the owner with a one-tap approval link. Stores may opt into trusted publishing for low-risk changes, but publishing remains logged and can be followed by one-tap rollback through `shopbuddy_rollback`.

## Setup and configuration

The hosted MCP endpoint is `https://getshopbuddy.vercel.app/api/mcp`. Claude Code can add it as an HTTP MCP server, and Codex can register the same URL. Cursor and VS Code provide install links in the project README. Claude web or desktop and ChatGPT can use the endpoint as a custom connector.

For hosted use, the agent opens a browser so the user can sign in or create an account and approve access.

The shopbuddy MCP server also has a Claude Code plugin installation path. Installing the plugin adds the Shop Buddy skill in addition to the MCP connection. The hosted service is independent and is not affiliated with or endorsed by Shopify.

## Tools and capabilities

Documented MCP tools include:

- `shopbuddy_start_change` to create a staging copy and working session.
- `shopbuddy_validate` to run Theme Check.
- `shopbuddy_push_preview` to upload changes and capture comparison screenshots.
- `shopbuddy_submit` and `shopbuddy_request_publish` to route a change for owner approval or publishing.
- `shopbuddy_rollback` to roll back a published change.

Together, these tools cover the documented workflow from staging and file edits through validation, visual inspection, approval, publishing, and recovery. The material does not enumerate separate tools for individual file operations; it describes file reading, searching, and writing as agent capabilities within the change workflow.

_Full upstream README: https://allmcps.com/mcp/shopbuddy-2/readme_