Printify MCP Server

Manage your entire Printify print-on-demand business from any AI assistant that speaks Model Context Protocol — Claude, Claude Code, Cursor, or any other MCP client. This Actor runs as a live MCP server on the Apify platform, so there's nothing to host yourself: connect your MCP client, hand it your Printify API token, and start asking it to browse the catalog, build products, place orders, or manage webhooks in plain English.

Why use the Printify MCP server?

Printify's dashboard is built for humans clicking through forms one product at a time. This Actor puts the same capabilities behind natural language instead:

• Bulk product creation — describe a product line and have your agent create dozens of variants across blueprints and print providers without touching a spreadsheet.
• Catalog research — ask "which print providers offer this hoodie blueprint and what do they charge for shipping to Germany?" and get a straight answer.
• Order automation — feed your agent a list of addresses and line items and let it submit, price, and send orders to production.
• No server to run — this Actor lives on Apify's infrastructure in Standby mode, always ready to accept a connection, with no deployment or uptime work on your end.

How to use the Printify MCP server

1. Get a Printify API token from Printify → My Profile → Connections (printify.com/app/account/api).
2. Get an Apify API token from your Apify Console integrations page — this authenticates you to the Actor itself, separately from Printify.
3. Connect your MCP client to this Actor's endpoint, passing both tokens as HTTP headers (see Connecting, below).
4. Start prompting: "list my Printify shops", "create a t-shirt product with this blueprint", "show me my last 10 orders".

Connecting

The MCP endpoint for this Actor is:

https://rl1987--printify-mcp.apify.actor/mcp

With the Claude Code CLI:

claude mcp add --transport http printify \
  https://rl1987--printify-mcp.apify.actor/mcp \
  --header "Authorization: Bearer ${APIFY_API_TOKEN}" \
  --header "x-printify-api-token: ${PRINTIFY_API_TOKEN}"

(export APIFY_API_TOKEN and PRINTIFY_API_TOKEN in your shell first — don't hardcode tokens in the command itself.)

For any other MCP client, add an HTTP/streamable-HTTP server with that URL and the same two headers.

Verify the connection and see the full tool list with claude mcp list or /mcp.

A shared .mcp.json (URL only, no tokens) can be committed to a team repo; each teammate then runs claude mcp add --scope local once with their own tokens.

Authentication

Every request needs two separate tokens, since the Actor and Printify are two different services:

Header	Purpose
Authorization: Bearer <token>	Your Apify API token — authenticates you to this Actor
x-printify-api-token: <token>	Your Printify API token — authenticates you to Printify's API

The Printify token is read fresh from the header on every tool call. The Actor never stores it, so different sessions can safely use different Printify accounts.

Tools

Every tool maps directly to a Printify API endpoint, grouped by resource:

Group	Tools
Shops	list_shops, disconnect_shop
Catalog	list_blueprints, get_blueprint, list_blueprint_print_providers, list_blueprint_variants, get_blueprint_shipping, list_print_providers, get_print_provider
Products	list_products, get_product, create_product, update_product, delete_product, publish_product, set_product_publish_succeeded, set_product_publish_failed, unpublish_product
Uploads	list_uploads, get_upload, upload_image, archive_upload
Orders	list_orders, get_order, create_order, send_order_to_production, cancel_order, calculate_order_shipping
Webhooks	list_webhooks, create_webhook, update_webhook, delete_webhook

Tools that take a product or order argument accept a raw JSON object matching the corresponding Printify request schema, documented in full at developers.printify.com. Your MCP client's model reads those docs and builds the payload for you — you don't need to hand-write JSON yourself.

Pricing

This Actor uses Apify's Pay Per Event model: each completed tool call charges the tool-call event (see .actor/pay_per_event.json for the current price). Failed calls — a bad Printify token, a Printify API error, a validation error — are never charged. There's no per-minute or standby cost; you only pay for tool calls your agent actually completes.

Tips

• Ask your agent to fetch list_blueprints and list_blueprint_print_providers before creating a product — it needs valid blueprint/print-provider/variant IDs to build a correct payload.
• Use calculate_order_shipping before create_order to sanity-check shipping cost and method without committing to an order.
• Idle MCP sessions are closed automatically after 5 minutes of inactivity (configurable via the SESSION_TIMEOUT_SECS environment variable) to keep the Actor's Standby container lean.

FAQ

Does this Actor store my Printify data? No. It's a stateless proxy — every tool call goes straight to Printify's API using the token in your request headers, and nothing is persisted.

Can multiple people use this Actor with different Printify accounts? Yes. The Printify token is per-request, so every caller can use their own account independently.

Something's not working — where do I report it? Open an issue on the Actor's Issues tab in Apify Console, or file one against this repository.

Did you find this useful?

⭐ Rate this actor on Apify! Your feedback helps other users find it and helps us keep improving it.