Shopify Dev MCP gives coding agents Shopify-aware documentation, schemas and validation. Shopify now recommends its broader AI Toolkit plugin for supported coding tools, while MCP remains an available integration path.
Key takeaways
- Focused on Shopify app and theme development context.
- Can validate GraphQL, Liquid and extension code against Shopify schemas.
- Store operations rely on the authenticated Shopify CLI context and should remain user-controlled.
What is Shopify Dev MCP?
Official Shopify developer MCP capability for current documentation, API schemas, code validation and supported store-development tasks. MCP standardizes how a compatible client discovers and invokes tools, but it does not make those tools safe automatically. The client, server, credentials and upstream service remain separate trust boundaries.
What tools does it expose?
- Search Shopify developer documentation and API schemas.
- Validate GraphQL queries, Liquid and extension configuration.
- Provide platform-specific implementation context.
- Prepare supported store-management tasks through authenticated tooling.
The exact catalog can change by release, account, enabled feature or server configuration. Inspect the live tool list and JSON schemas before enabling it. A descriptive tool name is not an authorization control, and a read-sounding operation can still reveal sensitive metadata.
What is a safe first test?
Validate one read-only GraphQL query and one small Liquid snippet in a development store project. Keep store-management actions manual until the exact Shopify CLI command and target store are visible.
Use a test account or project, allow only the required tools and record the client configuration, server version and arguments. Verify the result directly in the upstream service. Add write tools only after read-only behavior, authentication expiry, error handling and audit logs have been reviewed.
What data and credentials can it access?
Documentation and validation can receive code snippets and API queries. Store-management capabilities can use the authenticated Shopify CLI context and access the development store selected by the user.
Credentials should be supplied through the documented OAuth flow, a secret manager or a restricted environment variable, never pasted into prompts or committed to source. The upstream account should expose only the resources required for the pilot.
Which permissions should you grant?
- A development store rather than a merchant production store.
- A dedicated Shopify partner or staff identity with minimum access.
- Manual confirmation for Shopify CLI actions.
Prefer project-scoped, read-only or restricted tokens. Where the server offers tool filters, combine them with upstream authorization rather than treating filtering as the only control. Separate development and production identities and rotate test credentials after the evaluation.
What should a security review cover?
- Do not send customer or order data in validation prompts.
- Verify the target store before every authenticated command.
- Keep app secrets and access tokens outside agent context.
Assume tool results can contain prompt injection or hostile content. Keep approval gates in application code for financial, administrative, destructive or public actions. Apply network restrictions, timeouts, output-size limits and audit logging at the host or gateway layer.
What are the main limitations?
- The recommended installation path may be the AI Toolkit plugin rather than raw MCP.
- Supported clients and tools can change with Shopify tooling.
- Validation cannot replace testing against the selected API version.
This is a documentation-based profile checked on 2026-10-04; Anavem did not connect the server or test it against a live account. Tool catalogs, transport support, pricing, licensing and authentication methods can change. Verify the current first-party documentation before installation.