Printful
Connect Printful to browse the print-on-demand catalog, push products to your store, create and fulfil orders, upload print files, generate mockups, and rate-shop shipping.
You end up with one Printful private token, created in the Printful Developer Portal, that you paste into PopMCP's Private token field.
- Setup time
- 5 min
- Auth
- API credentials
- API base URL
- https://api.printful.com
- Rate limits
- 120 API calls per minute overall, with tighter limits on heavy endpoints such as the mockup generator.
Before you begin
- A Printful account with at least one store already created.
- Sign-in rights to that account. The Developer Portal logs you in through Printful's own OAuth screen.
- A contact email for the token. The form requires one.
- Decide whether the token covers one store or the whole account. Account-level tokens need an X-PF-Store-Id header on store endpoints.
- Private tokens carry an expiry date and cannot be refreshed, so plan to replace the token before it lapses.
Get your credentials
Sign in to the Printful Developer Portal
Go to developers.printful.com and click Sign in to Printful. Approve the Printful sign-in screen to land back in the portal.
Open Tokens and add a new one
In the left menu click Tokens, then click Add new token.
Your tokens
Create private tokens and get access to your Printful store API
| Token name | Created on | Expires on | Scopes |
|---|---|---|---|
| Storefront syncMy Test Store | Mar 4, 2026 | Mar 4, 2027 | Orders, Sync products+1 more |
| Old importerMy Test Store | Feb 2, 2025 | Feb 2, 2026 | File library |
You haven't created any tokens yet
Generate authentication tokens for your personal projects.
Fill in the details, expiry and access level
Enter PopMCP under Token name and an address under Contact email. Pick an Expiration date, then choose A single store and select your store from the dropdown.
Add new token
Set up your private token and manage its permissions
Tick the scopes and create the token
Under Scopes tick Orders, Sync products and File library, plus Webhooks if PopMCP should manage subscriptions. Click Create new token.
Add new token
Set up your private token and manage its permissions
Read-only variants exist for each scope, such as orders/read instead of orders.
Copy the access key into PopMCP
Copy the value in the Access key panel, then paste it into PopMCP's Private token field.
PopMCP
Set up your private token and manage its permissions
PopMCP sends the token as an Authorization: Bearer header.
Connect in PopMCP
Open your workspace, choose Printful in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Private tokensecret | In Printful, open the Developer Portal (developers.printful.com) → Your tokens → create a private token, grant the scopes you need (orders, sync products, file library, webhooks, …), and copy it (it is shown only once). Sent as an Authorization: Bearer header, stored encrypted, used server-side only.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Printful immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
The Printful connector in PopMCP shows Connected and a catalog or store-information call returns your store name rather than a 401.
Troubleshooting
401 Unauthorized
Why: The token expired, was deleted in the Developer Portal, or the Bearer prefix got mangled on paste.
Fix: Check the Expires on date under Your tokens and create a replacement if it has lapsed.
You navigated away before copying the access key
Why: The Access key panel shows the secret once, and Printful does not store it.
Fix: Delete the token under Your tokens and create a new one.
403 on a specific endpoint while others work
Why: That endpoint needs a scope the token was not granted, or you granted the read-only variant.
Fix: Create a new token with the missing scope. Scopes cannot be added to a token after creation.
Calls fail with a missing store error
Why: An account-level token was used on an endpoint that needs store context.
Fix: Create a store-level token for the store you want, or make sure PopMCP is configured to send X-PF-Store-Id.
429 Too Many Requests
Why: More than 120 calls in a minute, or a stricter per-endpoint limit such as the mockup generator.
Fix: Back off and retry. Batch mockup generation rather than firing requests in parallel.
Reference
Okendo
Connect Okendo to manage storefront reviews and ratings, photo and video media, AI review summaries, and loyalty.
Printify
Connect Printify to browse the print-on-demand catalog, upload artwork, build, price, and publish products, and place, price, approve, cancel, and track orders across your shops.