Shopify storefront MCP moved to /api/ucp/mcp: update the URL, add Sume
Shopify's storefront MCP now lives at https://{shop}/api/ucp/mcp, not /api/mcp. Update your agent, then add Sume at mcp.sume.com/mcp for product video.
Shopify's storefront MCP page now lists https://{shop}/api/ucp/mcp, under the Universal Commerce Protocol, next to the older https://{shop}/api/mcp path. If your agent still points at the old path, change the URL and add the agent profile that the new endpoint requires on every request. Then add Sume as a second server if you want the agent to make a product video from the catalog data.
I read the Shopify page on 2026-10-05; check it for the current status of the old path before you cut over.
Old and new
| Item | Old | New |
|---|---|---|
| URL | https://{shop}/api/mcp | https://{shop}/api/ucp/mcp |
| Protocol | Storefront MCP | Universal Commerce Protocol (UCP) |
| Tools listed | See the Shopify page | search_catalog, lookup_catalog, get_product, create_cart, get_cart, update_cart, cancel_cart |
| Agent profile | See the Shopify page | Required on every request |
| Checkout | See the Shopify page | Authenticated or signed |
Add Sume next to it
Sume has one hosted MCP endpoint for account, catalog, job, asset, generation and crawl tools. A remote MCP client such as Claude Code connects with two commands, then asks for a read-only tool to confirm the session.
claude mcp add --transport http sume https://mcp.sume.com/mcp
claude mcp login sumeDivision of labour
| Step | Server | Tool |
|---|---|---|
| Find products | Shopify | search_catalog or lookup_catalog |
| Get one product | Shopify | get_product |
| Make a clip | Sume | generate_video with an idempotency_key |
| Wait for it | Sume | jobs_wait, then jobs_result |
| Build a cart | Shopify | create_cart, update_cart |
Notes
- Use dry_run first. It previews admission and cost without submitting.
- The default OAuth grant on Sume is read only (mcp:read). Paid generation needs the Write toggle on the consent page, or an API key.
- Image 1.0 and Video 1.0 are not on hosted MCP; generate_video routes to the video router instead.
- Sume's docs do not describe a Shopify connector, so passing product data from one server to the other is the agent's job.
Sources
Related posts
More in Integrations
- Slack image block with a Sume URL: PNG or JPEG, alt text required
Slack's image block takes a public image_url up to 3000 characters and lists png, jpg, jpeg and gif. Generate a png with Sume, then post it with alt_text.
- Slack connector stopped working after an hour? Reconnect in Sume
When Slack returns no token expiry, Sume assumes one hour. After that an admin must connect again, because v1 has no automatic token renewal for integrations.
- Slack MCP has no dynamic registration: how Sume connects anyway
Slack's MCP server needs a registered Slack app with a client secret and does not support Dynamic Client Registration, so Sume uses its own Slack app.
- Slack consent worked but MCP rejects the app: enable Slack MCP
If Slack OAuth consent succeeds but MCP initialization is rejected, the Slack app has not enabled the Slack MCP server. It is a separate switch from Agents.
Written by Sume