
Shopify Store Builder Mcp
io.github.nazariinalyvaikobsPublished by GitHub account nazariinalyvaikobsv0.1.1Updated Oct 24, 2026
MCP server for building Shopify stores via the Admin GraphQL API: themes, pages, and navigation
Overview
Lets an assistant build and manage a Shopify store through the Admin GraphQL API: themes, pages, menus, products, orders, and discounts.
- What you can do
- Runs locally and talks directly to one configured Shopify store (and optionally a Horoshop store) over the Admin GraphQL API. Shopify tools cover store info, theme listing, import, duplication, publishing, theme file reading and editing, theme media slots and uploads, pages, menus, products and variants, inventory, customers, orders, fulfillment, discounts, and native sales reports. Horoshop tools cover categories, products, reviews, customers, orders, and order summaries. Tools are grouped by platform and resource, and each is tied to one configured store.
- When to use it
- Use it when an assistant should make real changes to a Shopify storefront or catalog, such as editing theme files, publishing a theme, creating pages or menus, managing products and inventory, or reading orders and sales metrics. It suits merchants or developers who want store administration driven from an MCP client rather than the Shopify admin UI.
- Requirements
- Node.js for the npm package, run via npx or an MCP client config. Needs SHOPIFY_STORE_DOMAIN plus either SHOPIFY_CLIENT_ID and SHOPIFY_CLIENT_SECRET or an existing SHOPIFY_ADMIN_ACCESS_TOKEN. Optional Horoshop support needs its store URL, login, and password. Network access to the store APIs; Chrome installed locally for Horoshop review reading.
Installation
In SourceWeft
- Open Shopify Store Builder Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.
- License10 pts
Declare a license in the repository or the registry entry.