Self-hosted Shopify Dev MCP MCP alternatives
Shopify's dev MCP server installs and runs locally, so the process stays on your own machine while it helps you build against Shopify's API. It is worth remembering what it does: it serves docs and validates code, it does not touch a live store. Each pick here also runs self-hosted over stdio.
Keeping the process local controls where it runs and where any key lives. For the commerce and payments picks, the store and payment data still travel to each product's own API over the network; self-hosting the server is about the connector, not the data path.
The 8 best self-hosted alternatives
The same kind of tool, run locally: BigCommerce's server grounds agents in developer docs, REST and GraphQL APIs, webhooks, OAuth scopes, and code examples, helping you build the integration on your own machine.
Set up BigCommerce →- WooCommerceOfficial
WooCommerce's integration runs locally and actually manages a store: query products and orders, create and update products, and add order notes. It is store operations rather than the docs work Shopify's dev server does.
Set up WooCommerce → Razorpay's server runs self-hosted and creates orders and payment links, captures and refunds payments, and reads settlements, keeping the payments connector on your own infrastructure.
Set up Razorpay →Run locally, this server reaches the full Square API through make_api_request, covering payments, catalog, orders, customers, bookings, and inventory for in-person and omnichannel selling.
Set up Square →Installed locally, the Paddle server manages the product catalog, billing, subscriptions, and reports through the Paddle Billing API, a merchant-of-record option for software products.
Set up Paddle →Self-hosted, the Adyen server creates payment sessions and links, refunds and cancels payments, and manages merchant accounts, terminals, and webhooks, with the process on your side.
Set up Adyen →Mercado Pago's locally run server helps integrate payments: search docs, generate code, score integration quality, and test webhooks. It is integration tooling for the Mercado Pago API.
Set up Mercado Pago →- KlaviyoOfficial
Adjacent rather than a swap: Klaviyo's server runs locally and manages profiles, campaigns, flows, lists, segments, and events with reporting. It is marketing automation around a store, not store or docs management.
Set up Klaviyo →
How to choose
All of these run on infrastructure you control like Shopify's dev server. BigCommerce is the direct counterpart for developer docs; WooCommerce is the self-hosted store-operations pick; Razorpay, Square, Paddle, Adyen, and Mercado Pago each cover a payments model; Klaviyo handles marketing. Decide by task, and note that the commerce and payment servers still call their vendor APIs over the network even when run locally.
FAQ
- Can the Shopify Dev MCP server be self-hosted?
- Yes. It installs and runs locally, so the process stays on your own machine. It is a developer-docs and validation server, though, so what stays local is the docs and code-validation tooling, not live store data, which it never touches.
- Which self-hosted alternative actually manages a store?
- WooCommerce. Its locally run integration queries and manages products and orders directly, unlike Shopify's dev server, which only serves docs and validates code. The payments servers here, Razorpay, Square, Adyen, and the rest, run locally too but handle checkout rather than catalogue management.