zed -shopify-dev

This MCP server bridges Shopify’s developer context capabilities into Zed’s Assistant via the dev-mcp framework. It boots a Shopify Dev MCP context server that exposes contexts and commands useful for building and testing Shopify-related workflows within Zed. Once running, you can query available Shopify development contexts (for example, store, theme, and app development contexts) and invoke commands that help you simulate or test Shopify development scenarios inside Zed. The integration relies on the dev-mcp toolchain, so you’ll interact with the same context surface that Shopify’s development tooling uses, but through Zed’s assistant interface for streamlined conversational or scripted automation.

Prerequisites:

• Node.js (recommended LTS version) and npm installed on your system.
• Internet access to fetch the MCP package via npx.

Installation steps:

1. Ensure Node.js and npm are installed. You can verify with: node -v npm -v

2. Run the MCP server using npx (this installs and runs the required package on demand): npx -y shopify-dev-mcp

3. By default, the server will start and listen for MCP requests. If you need to customize startup, set environment variables as described in the next section and then re-run the command.

4. (Optional) If your environment blocks npx caching, you can install the package locally first and then run it via Node.js as per the package’s instructions.

Note: If you are behind a proxy or corporate network, ensure your proxy settings are configured for Node/npm before executing the commands.

Environment variables and configuration options may be required for authentication with Shopify APIs. Common placeholders to consider:

• SHOPIFY_API_KEY: Your Shopify API key
• SHOPIFY_API_SECRET: Your Shopify API secret
• SHOPIFY_STORE: Target store domain or identifier
• MCP_LOG_LEVEL: Debug, info, warn, error (optional)

If you encounter connectivity or authentication issues, verify that the Shopify credentials are valid and that network access to Shopify’s API endpoints is allowed from your environment. Check that the dev-mcp dependency is up to date and that there are no port conflicts with other services running on your machine.