MCP server
Connect an AI assistant to your Seamdex organization through the Model Context Protocol. Available on the Enterprise plan.
Overview
The MCP server gives an assistant such as Claude or ChatGPT a set of tools over your product records: search styles and purchase orders, see what blocks a passport from publishing, read EPR figures for a period, edit product sections and publish. It runs the same checks and writes the same Activity entries as the app and the REST API. Deleting records and importing purchase orders stay in the app and the REST API.
The server address is:
https://www.seamdex.com/api/mcpConnecting
Claude (web and desktop). In Settings, Connectors, add a custom connector with the address above. Claude opens a Seamdex sign-in: sign in, pick the organization and allow the access listed.
ChatGPT. Where your plan offers custom connectors in developer mode, add a connector with the same address and sign in the same way.
Claude Code, Cursor, VS Code and your own agents. Use Seamdex sign-in where the client supports it, or an organization API key from Settings, API Keys sent as a bearer header:
claude mcp add --transport http seamdex https://www.seamdex.com/api/mcp \
--header "Authorization: Bearer sdx_..."Access
Only owners, editors and viewers of an organization with Enterprise API access can connect; partner and supplier logins cannot. A sign-in connection can do what the member allowed on the consent screen and no more than their role permits: viewers read, editors and owners can also edit and publish. An API key can do what its scopes allow.
| Consent line | Scope | Same as API key scopes |
|---|---|---|
| Read products, purchase orders, passports and EPR figures | mcp:read | Products: Read, Purchase Orders: Read |
| Edit product records | mcp:write | Products: Update |
| Publish passports, which makes them public and counts toward billed style passports | mcp:publish | Products: Publish |
Owners see every connected assistant in Settings, API Keys, and can disconnect one there; access ends at once. Changes an assistant makes show in Activity as the member via AI assistant.
Tools
Assistants only see the tools their connection allows. Tools that change data are marked, so assistants ask before using them.
| Tool | What it does | Needs |
|---|---|---|
about_seamdexRead-only | What Seamdex is and does, the terms it uses (product, purchase order, passport, style passport, EPR, libraries), pricing, its regulatory position and links to the help centre and documentation. | Any connection |
whoamiRead-only | The Seamdex organization this connection works in, who connected it and which actions it allows. | Any connection |
search_productsRead-only | Find products (garment styles) by style number or name, status, season or purchase order. Returns ids, status and passport counts, newest first. | Products: Read |
get_productRead-only | One product record: basics, composition, trims, packaging, care, compliance, colourways, variants and its passports. | Products: Read |
get_product_readinessRead-only | What blocks a product from publishing (errors) and what is incomplete but allowed (warnings). "ready" means publish_product would succeed. | Products: Read |
list_product_revisionsRead-only | The published versions of a product, newest first, with who published each and when. | Products: Read |
search_purchase_ordersRead-only | Find purchase orders by number or supplier. Returns ids, dates and how many styles are published or ready. | Purchase Orders: Read |
get_purchase_orderRead-only | One purchase order with every style on it and each style's publish readiness. | Purchase Orders: Read |
list_passportsRead-only | Published Digital Product Passports with their public URLs, one per size or colour. Filter by product, purchase order or GTIN. | Products: Read |
get_passportRead-only | One passport by its passport id, with its public URL and the product it belongs to. | Products: Read |
get_epr_reportRead-only | Extended Producer Responsibility figures for a period: garments, fibre weights and packaging by material. Period by purchase order ETA or by publish date. | Products: Read |
get_epr_filing_previewRead-only | The declaration figures for one EPR scheme and period: totals per scheme category, per-product rows, and products or purchase orders that still need mapping. Nothing is filed. | Products: Read |
update_productChanges data | Replaces whole sections of a product record (mode, basics, identity, composition, trims, packaging, care, performance, compliance, colorways, variants, importedComposition, listing). A section sent here overwrites the stored section, so fields left out of it are cleared. A published product keeps its live passport until it is published again. | Products: Update |
publish_productChanges data | Publishes one product: its passports go live on public URLs and newly published styles count toward the organization's billed style passports. Fails with the blocking fields when the product is not ready. | Products: Publish |
publish_purchase_orderChanges data | Publishes every ready draft on a purchase order, up to 100 per call, and lists the drafts it skipped with their blockers. Passports go live on public URLs and count toward billed style passports. | Products: Publish |
Limits
Each connection has 600 requests a minute, within the organization's 2000 a minute shared with the REST API. Publishing is limited to 60 products and 5 purchase orders a minute. Publishing makes passports public at once, and each newly published style counts toward your billed style passports, exactly as in the app.