Shopify Dev (official)
Capped at 90: 1 of 2 real tool calls passed in our test; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 90 because not every real tool call passed. Not a quality or security rating. Why scores are capped
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tool-call test (2026-11-10, direct MCP stdio client, no LLM): pass. 1 of 2 real function calls passed in the 2026-11-10 stale retest. Evidence: local test run, Nov 10, 2026.
Transport (tested 2026-10-22): stdio
Tested version: 1.17.0 · tested 2026-10-22
Token cost (estimate): approx. 5527 tokens, cl100k estimate (5 tools, measured 2026-11-11, version 1.18.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 1 read, 3 write (state-changing), 1 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
feedback— unclassifiedlearn_shopify_api— write (state-changing)search_docs_chunks— readvalidate— write (state-changing)validate_theme— write (state-changing)
handshake and tools listed without a recorded key or OAuth
Score 90/100 · Tools 5 · Token cost approx. 5,527 tokens · Compare · Last tested 2026-11-10 · Version tested 1.18.0 · Package @shopify/dev-mcp · Repo shopify.dev docs
Summary: Shopify Dev (official) completed an MCP handshake without credentials and exposed 5 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 5
- Context cost
- approx. 5527 tokens, cl100k estimate (5 tools, measured 2026-11-11, version 1.18.0; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-10
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @shopify/dev-mcp (Node 20, Linux) succeeded in 9s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 5 tools listed in 6.6s. |
| maintenance | pass | 25 | Latest release published 5 days before test. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | ISC (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 5527 tokens, cl100k estimate for 5 tools · about 67% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): low.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-10
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 5 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Checked on 2026-11-09 for version 1.17.0 against OSV, GitHub advisories. Scope: the package itself; dependencies not scanned.
No published advisories found in OSV and GitHub advisories for @shopify/dev-mcp 1.17.0 as of 2026-11-09. This is not a security audit.
⚠ Check is out of date.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Unchanged since the previous snapshot (latest 2026-11-11).
Snapshot hash (fingerprint of the tool list)
4ec081b1c5de: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@shopify/dev-mcp",
"version": "1.18.0",
"registry": "npm",
"status": "working",
"tested": "2026-11-10",
"tools_count": 5,
"deprecated": false,
"archived": null,
"tests": {
"install": [
"pass",
20,
"`npm install @shopify/dev-mcp` (Node 20, Linux) succeeded in 9s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 5 tools listed in 6.6s."
],
"maintenance": [
"pass",
25,
"Latest release published 5 days before test."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"ISC (OSI-approved)."
]
}
}Install
npx -y @shopify/dev-mcp
Pin the version we tested
npx -y @shopify/dev-mcp@1.18.0
tested 2026-11-10. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"shopify-dev": {
"command": "npx",
"args": [
"-y",
"@shopify/dev-mcp@1.18.0"
]
}
}
}Tools listed
feedback, learn_shopify_api, search_docs_chunks, validate, validate_theme
Tool history: captured Nov 11, 2026. All tool history.
Quick config
{
"mcpServers": {
"shopify-dev": {
"command": "npx",
"args": [
"-y",
"@shopify/dev-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @shopify/dev-mcp(Node 20). This is the exact command we ran on 2026-11-10. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (5 in our test).
{
"mcpServers": {
"shopify-dev": {
"command": "npx",
"args": [
"-y",
"@shopify/dev-mcp"
]
}
}
}Test history
- 2026-11-10: Retested
- 2026-10-22: New
Related: Best docs MCP servers
FAQ
Is Shopify Dev deprecated?
No. @shopify/dev-mcp was not deprecated or archived when we last tested it on 2026-11-10.
What replaces Shopify Dev?
Nothing; Shopify Dev (official) is not deprecated as of 2026-11-10.
Does Shopify Dev need an API key?
No. It completed an MCP handshake with no credentials and listed 5 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.