# Printify MCP by usefulapi

> Printify MCP by usefulapi is an MCP server. Read shops, catalog blueprints, print providers, products and orders; create and publish products. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Website:** https://usefulapi.io/printify/
- **Repository:** https://github.com/m190/usefulapi-mcp/tree/HEAD/servers/printify
- **MCP Registry name:** io.usefulapi/printify
- **Listing updated:** 2026-11-13

## About

Read shops, catalog blueprints, print providers, products and orders; create and publish products.

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http printify https://printify.usefulapi.io/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://printify.usefulapi.io/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "printify": {
      "url": "https://printify.usefulapi.io/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "printify": {
      "type": "http",
      "url": "https://printify.usefulapi.io/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "printify": {
      "serverUrl": "https://printify.usefulapi.io/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "printify": {
      "type": "http",
      "url": "https://printify.usefulapi.io/mcp"
    }
  }
}
```

## Tools

- `printify_create_order`: WRITE: preview an order of existing enabled product variants in an API/custom-integration store. Set this exact store to Manual approval in Printify BEFORE confirmation, then pass manual_approval_confirmed:true, confirm:true and the approved preview_hash. The API cannot verify Manual approval; auto-approval can otherwise cause production/charges. Persistent operation_id prevents automatic duplicat
- `printify_send_to_production`: WRITE: separately preview and approve production of an existing order, including its destination and fulfillment costs. Can charge your linked Printify payment method. Requires production_charge_approved:true, confirm:true and preview_hash; use the same operation_id for retries. Uncertain submissions are never replayed.
- `printify_create_webhook`: WRITE: preview an order/shipment topic and HTTPS receiver; confirm with preview_hash to register it. Uses the signing secret configured securely on the connection, never a tool argument or result. Shares event data with that receiver. Verify X-Pfy-Signature at your receiver; API acceptance is not proof of signature delivery. Duplicate/uncertain attempts are not blindly replayed.
- `printify_delete_webhook`: WRITE: preview a shop's selected webhook, check expected_host against its destination, then confirm with preview_hash to delete only that webhook. Uses Printify's required host query safeguard and persistent operation deduplication.
- `printify_update_product_prices`: WRITE: preview integer-cent retail price changes on selected variants. Confirm with preview_hash to update Printify, preserving all other variants, flags, SKUs and defaults; verify readback. Does not publish to an external sales channel. Reuse operation_id rather than blindly repeating an uncertain update.
- `printify_write_operation_status`: Read the persistent state and known resource IDs for an operation on this connection in a shop authorized by the current token. Does not create, submit, update or delete anything. Reconcile an uncertain attempt before doing further writes or rotating the token; operation history is scoped to the original connection identity.
- `printify_copy_products`: Preview or copy selected products or a complete catalog between two Printify shops in the same account. Preserves title, description, blueprint/provider, variant IDs/prices/enabled flags, artwork IDs and print-area transforms. Preserves canvas side printing and image pattern rotation. This initial workflow does not copy tags, SKUs, channel IDs, publication state or generated mockups. Products with
- `printify_copy_status`: Read a durable product-copy job's progress, target mappings, failures and uncertain writes. Verifies that the current token can access both shops. Does not create or retry products.
- `printify_resolve_copy`: Resolve one failed or uncertain source product in a durable copy job. Provide an existing target_product_id to verify the exact supported fields against the checkpoint and record it as copied. Or set verified_not_created:true only after checking the target shop manually; this allows one future retry through printify_copy_products. Requires confirm:true, never creates/publishes/deletes anything its
- `printify_list_shops`: List all shops connected to the Printify account. This is the entry point — each shop's `id` is required by the product, order and webhook tools. Printify REST: GET /v1/shops.json.
- `printify_list_products`: List products in a shop (paginated). Printify REST: GET /v1/shops/{shop_id}/products.json.
- `printify_get_product`: Get a single product's full details (variants, images, print areas, publish status). Printify REST: GET /v1/shops/{shop_id}/products/{product_id}.json.
- `printify_list_orders`: List orders in a shop (paginated), optionally filtered by status or SKU. Printify REST: GET /v1/shops/{shop_id}/orders.json.
- `printify_get_order`: Get a single order's full details, including `shipments` (carrier + tracking numbers). Printify REST: GET /v1/shops/{shop_id}/orders/{order_id}.json.
- `printify_calculate_shipping`: Get a shipping price quote for a set of line items to a destination address. Non-destructive — it only prices, it does NOT place an order. `line_items` is an array where each item is one of {product_id, variant_id, quantity}, {print_provider_id, blueprint_id, variant_id, quantity}, or {sku, quantity}. `address_to` is the destination (first_name, last_name, email, phone, country, region, address1, 
- `printify_list_catalog_blueprints`: List all blueprints (product types, e.g. 'Unisex T-Shirt') available in the Printify catalog. Printify REST: GET /v1/catalog/blueprints.json.
- `printify_get_blueprint`: Get a single catalog blueprint's details. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}.json.
- `printify_get_print_providers`: List the print providers that can produce a given blueprint. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}/print_providers.json.
- `printify_get_variants`: List the variants (sizes, colors) a print provider offers for a blueprint. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}/print_providers/{print_provider_id}/variants.json.
- `printify_list_print_providers`: List all print providers in the Printify catalog. Printify REST: GET /v1/catalog/print_providers.json.
- `printify_list_webhooks`: List the webhooks configured for a shop. Printify REST: GET /v1/shops/{shop_id}/webhooks.json.
- `printify_list_uploads`: List images uploaded to the account's media library (paginated). Printify REST: GET /v1/uploads.json.
- `printify_publish_product`: Publish a product to the shop's connected sales channel (e.g. Shopify, Etsy). STATE-CHANGING: this locks the product and pushes the selected fields to the external store. The body is an object of booleans controlling which fields are published; all default to true. Printify REST: POST /v1/shops/{shop_id}/products/{product_id}/publish.json.

## FAQ

### How do I add Printify MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http printify https://printify.usefulapi.io/mcp

---
Source: https://ai-powered.com/mcp/printify-mcp-by-usefulapi
