Getting started
Peak PIM MCP connector
A remote Model Context Protocol server that lets AI assistants work on your catalog: browse products, compare stores, audit data health, draft edits, and — if you allow it — publish to Shopify. You authorize each connection in your browser and choose exactly how much it can do.
At a glance
| Connector URL | https://api.peak-pim.com/mcp |
|---|---|
| Transport | Remote MCP (streamable HTTP) |
| Authentication | OAuth 2.1 — dynamic client registration, PKCE, refresh tokens. No API key to copy around. See Authorization & consent. |
| Permissions | Three consent tiers: read · read & write · read, write & publish |
| Works with | Claude (web/desktop connectors, Claude Code), ChatGPT (developer mode), Cursor, and any MCP client that supports remote servers with OAuth |
| Tools | 28 tools — 22 reads, 5 draft-side writes, 1 publish |
What an assistant can do with it
- "List my products and show me which ones have unpublished changes."
- "Show me product Trail Runner 2 on each of my stores — where do the titles or prices differ?"
- "Which markets sell in EUR, and through which catalogs?"
- "What is scheduled to change on this product, and when?" (Drops)
- "Run a completeness scan and fill the missing SEO titles as drafts." (write tier)
- "Publish product X to all my stores and tell me exactly what succeeded and what failed." (publish tier)
28 tools, three scopes
The catalog is 28 versioned (_v1) tools: 12 entity tools over the
core catalog (products, collections, variants, per-store versions) and 16
operations tools (markets, metafield and metaobject definitions, translations,
sales channels, Drops, data health). By scope:
| Scope | Tools | What they touch |
|---|---|---|
read pim:read | 22 | Browse and compare — 20 read only Peak PIM's own rows; 2 sales-channel reads query Shopify live. |
write pim:write | 5 | Draft edits only: 2 attribute patches, 2 data-health remediation batches, and 1 non-destructive scan recompute. Nothing reaches Shopify. |
publish pim:publish | 1 | publish_master_v1 — the only tool that mutates Shopify. |
There is no delete: no tool deletes data, and a delete permission is not grantable at all.
Consent tiers
Adding the connector opens a browser consent page on the Peak PIM app. The consent screen shows who is asking and offers up to three permission tiers. You pick one (or deny):
| Tier | Scopes granted | Allows |
|---|---|---|
| Read | pim:read | Browse and compare the catalog. Nothing can be changed. |
| Read & write | pim:read pim:write | Also edit draft values — nothing reaches Shopify until a person (or a publish-tier connection) publishes. |
| Read, write & publish | pim:read pim:write pim:publish | Also push items live to your Shopify stores. |
The pim:publish scope can only be granted through this consent screen — never through any other credential surface. A tool outside the granted tier fails with a clear permission error and re-authorization guidance. Full details in Authorization & consent.
Where to go next
Quickstart
Connect Claude, Claude Code, ChatGPT, Cursor, or any OAuth-capable MCP client, and verify with a first prompt.
Getting startedAuthorization & consent
The OAuth 2.1 flow, discovery endpoints, the three tiers, token lifetimes, and how to revoke a connection.
Getting startedSecurity & limits
Tenancy from the token, minimized data-only results, and the operational limits every tool call runs under.
ReferenceTool index
All 28 tools with their scopes, one-line behavior, and links to the per-group detail pages.