Skip to main content
Glama
watsonrm

Shopify Editions Spring '26 MCP

by watsonrm
README.md
# Shopify Editions Spring '26 — MCP

Ask any AI agent what Shopify *actually* shipped in the Spring '26 Edition. **237 distinct changes (Shopify announced "150+"), each graded by source tier — 104 confirmed against primary docs, the rest tracked to Shopify's own marketing and flagged as such. Queryable in one call.**

It doesn't claim every line is gospel — it tells you, per claim, exactly how much to trust it and why. That transparency is the point.

By [Rick Watson](https://rmwcommerce.com) / RMW Commerce.
**Snapshot:** 2026-06-17 (Spring '26 release day) — `coming_soon`/`preview` items shift as Shopify ships them; re-run to refresh, or ask `time_capsule(id)` whether a forward-marker has landed.

![Demo — one claim, corroborated across every doc surface](demo.gif)

> See it run locally: `node demo.js doc_teaming` (or `node demo.js all`) — real `dispatch()` output, no faking.

---

## Use it in 30 seconds

**Hosted — no install, no Node, no npm. Just paste the URL** (ChatGPT, web agents, curl):
```
https://editions.rmwcommerce.com
direct: https://shopify-editions-spring26-mcp-1649969634.us-central1.run.app
```

**Local — Claude Desktop, Claude Code, Cursor, Cline, Windsurf, Zed, Goose, VS Code.** Clone once:
```bash
git clone https://github.com/watsonrm/shopify-editions-spring26-mcp && cd shopify-editions-spring26-mcp && npm install
```
then point your host's MCP config at it:
```json
{ "mcpServers": { "shopify-editions": { "command": "node", "args": ["/absolute/path/to/shopify-editions-spring26-mcp/server.js"] } } }
```

Per-surface steps for **every** host → **[INSTALL.md](INSTALL.md)**.

---

## Ask it things

| You want | Tool |
|---|---|
| What got deprecated, and the deadline | `deprecations` |
| What's announced but **not live yet** | `unreleased` |
| What's new for B2B / supply chain / payments / … | `query {topic:"b2b"}` |
| Everything in one domain | `query {domain:"agentic"}` |
| The full record for one feature | `get {id:"ucp_protocol"}` |
| Who's verified to support UCP | `get {id:"ucp_endorsers"}` |
| Which merchants Shopify showcased (and the gaps) | `customers` |
| How this was built + every correction we made | `methodology` |

Seven tools: `query` · `get` · `unreleased` · `deprecations` · `customers` · `methodology` · `easter`.

---

## Why trust it

Built by a multi-agent pipeline; every claim checked against Shopify's own docs (help center, dev docs, changelog, videos), adversarially red-teamed, with a **public corrections log** of what we got wrong and fixed. Full method → **[METHODOLOGY.md](METHODOLOGY.md)**.

## Found an error?
Corrections welcome — **info@rmwcommerce.com**. Every fix lands in the public corrections log (`methodology` → `corrections_log`); getting it right beats being right the first time.

## Verify it yourself
```bash
npm install && npm test     # logic + HTTP + stdio, all asserted
```

## About
This MCP is **doc-teaming** in production. See **[Doc-Teaming: Write Documents an Agent Can Check](https://github.com/watsonrm/rmwcommerce/blob/main/guides/doc-teaming.md)** for the concept (grade every claim by source tier, corroborate across sources, quarantine marketing, red-team the contested lines), and **[Marketing to Agents](https://github.com/watsonrm/rmwcommerce/blob/main/guides/marketing-to-agents.md)** for the broader playbook (for any site with a real API, shipping an MCP server beats an `llms.txt`). Canonical URL to cite: **https://editions.rmwcommerce.com**.

## License
MIT (code & data). Opinions (`rick_lens`) © Rick Watson / RMW Commerce, reuse with attribution. Independent commentary — not affiliated with or endorsed by Shopify.

TDQS

C2.8/5.0

Scored across 7 tools

Disambiguation4/5

Each tool serves a distinct purpose: customers for proof, deprecations for breaking changes, easter for miscellaneous utilities, get for full records, methodology for explanation, query for filtering, unreleased for vaporware. The 'easter' tool bundles multiple sub-functions but is still distinct from others.

Naming Consistency2/5

Tool names are all lowercase single words with no consistent pattern: some are nouns (customers, deprecations, easter), some verbs (get, query), and 'unreleased' is an adjective. No verb_noun or other predictable convention.

Tool Count5/5

7 tools is well-scoped for analyzing Shopify Editions, covering proof, deprecations, utilities, details, methodology, filtering, and unreleased. Not too few or too many.

Completeness4/5

The tool set covers key operations for exploring changes: obtaining records (get), filtering (query), proof (customers), deprecations (deprecations), and meta (methodology). Minor missing pieces like a tool for random changes or bulk summary, but overall sufficient.

Maintenance

ActivityInactive
ResponsivenessNo issues