VistaPrint

Search VistaPrint products, compare prices and design from templates in Claude, then add the design to your cart.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the VistaPrint connector does

The VistaPrint MCP server lets Claude search VistaPrint's print catalogue, configure and price products, design from templates or your own images, preview the result and add it to your VistaPrint cart. It exposes 19 tools. You cannot pay in the chat: checkout always happens on VistaPrint. Saved designs and past orders need a linked VistaPrint account.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

VistaPrint tools (19)

  • search_productsRead-only

    Search VistaPrint products by keyword for catalog discovery and downstream tool inputs. This tool returns data without selection UI. Each product url is an absolute product-page link for direct handoff. For multiple viable results when the user is ready to proceed and their preference remains unresolved, request_product_selection is the correct next interaction, naming only each candidate's productKey, productVersion, and a reason it fits; that tool resolves display fields and its own View link from the catalog, so platformUrl need not be carried forward. A prose recommendation does not resolve the required user-input checkpoint. Background research and requests to postpone choosing remain data-only, even with multiple results. Empty results and one exact clear product also bypass selection UI. Returns name, productKey, productVersion, priceFrom, imageUrl, galleryName, mpvId, url, and platformUrl. Carries no default/recommended option configuration; call product_details to resolve one.

  • request_product_selectionRead-only

    Display a focused shortlist of catalog-resolved products and wait for the user to type their choice. This tool is the required user-input checkpoint when multiple viable candidates remain, the user is ready to proceed, and their preference remains unresolved, including requests to see, compare, or choose among candidates. A prose recommendation does not replace this checkpoint. Input is a focused shortlist, preferably 3 to 6 products, naming only each candidate's productKey, productVersion, and a reason it fits; this tool resolves catalog display fields and the View link, and obtains prices at the default quantity or per-unit price ranges from the Pricing Platform, not from caller-supplied data. Candidates the catalog cannot resolve are omitted and reported with their requested position; the remaining products are renumbered consecutively. Background research, requests to postpone choosing, empty results, one exact match, and an already-selected product are outside its scope. This tool is terminal for its response; it names product_details as the next step, with no arguments, since that call resumes only once the user types their choice.

  • product_detailsRead-only

    Discover available options and quantities for a product, plus a sensible, quantity-compatible default configuration, given a productKey/productVersion from search_products. refine_product_selections resolves the final selection from these options and prices it in the same call.

  • refine_product_selectionsRead-only

    Preferred high-level tool for narrowing a product configuration and pricing it in the same call. Given partial/updated option selections, resolves them (like configure_product) and reports the resulting state — fullyResolved, partiallyResolved, or unresolvable — plus completed selections and remaining valid options. Prices requested pivots (default: Quantity) when the configuration is resolved enough; when it is not, returns configuration state plus an unpricedReason instead of guessing at a price. Selection keys must be option names exactly as returned by earlier product tools (including spaces and casing); unknown keys are rejected. configure_product and get_price remain available as lower-level building blocks.

  • configure_productRead-only

    Low-level building block: iteratively resolve a product configuration. With no selections, returns the full option set; with selections, resolves them against the current option set — the response reports the resulting completed selections and which options remain. Conflicting selections return an unresolvable state (not an error), with the remaining valid options for recovery. refine_product_selections combines this resolution with pricing in a single call and is the preferred tool for most configuration flows; this tool remains available for callers that want configuration state only.

  • get_priceRead-only

    Low-level building block: price one or more option×quantity combinations for a product in a single call — tax-aware, with product/shipping/item total breakdowns. Advisory/display-only: does not create or feed a cart. refine_product_selections combines configuration resolution with this pricing logic in a single call and is the preferred tool for most configuration flows; this tool remains available for pricing an already-fullyResolved configuration across a matrix of options and/or quantities directly.

  • search_templatesRead-only

    Search VistaPrint's template gallery for pre-designed templates. Only applicable when the product from search_products has a galleryName; products without one have no templates, so artwork comes from an external design tool via upload_asset instead. Results come from one resolved product configuration — the caller's selectedOptions completed into a full size/orientation/etc. set — so every returned template matches that single configuration; pass a different value in selectedOptions to see another size or orientation. Keywords narrow the gallery to the user's style, industry, or occasion; without them results are generic defaults. Returns up to 9 templates with preview images and templateTokens for create_document. When hasMore is true, repeat the same search with offset set to nextOffset to show the next 9.

  • begin_asset_uploadActs

    Start a single-file upload so a file the user attached to this chat can be imported with upload_asset. Returns an uploadId, an uploadUrl and an uploadCommand, valid for 30 minutes; one upload holds one file, so start a new one for each file. Try uploadCommand only if you can run code and the file is listed in /mnt/user-data/uploads: run it once with <path> replaced by that listed path, and when it succeeds call upload_asset with the uploadId. If the command fails for any reason (Could not resolve host / exit 6, host_not_allowed or 403, connection refused, a timeout, no network), do not retry it; and if code execution is off or no listed file matches, skip it. In all of those cases call show_asset_upload_picker with the uploadId, wait for the user to reply, then call upload_asset once. Aside: a workspace owner can allow allowlistDomain for code execution so the command works next time. Never base64-encode file contents, never invent or guess file paths, and never show uploadCommand to the user.

  • show_asset_upload_pickerActs

    Show an in-chat file picker for an upload started with begin_asset_upload; the picker sends the chosen file straight to that upload. Call it when uploadCommand failed for any reason (DNS, host_not_allowed, 403, connection refused, timeout, no network), code execution is off, or the file isn't listed in /mnt/user-data/uploads; do not retry the command first. Then wait for the user to reply in the chat, and call upload_asset with the uploadId once.

  • upload_assetActs

    Import artwork from a public HTTPS URL or in Claude `uploadId`, an upload session from begin_asset_upload holding a file the user attached to the chat and return a print-ready asset URL for use in edit_document operations (replaceImage or addImage). In Claude, when the user wants to use a file attached to the chat, call begin_asset_upload, deliver the file the way it describes, then pass its `uploadId` here instead of asking for an external URL. Confirm the returned file name with the user before placing it.

  • search_assetsRead-only

    List the user's own previously uploaded or accessible image assets, newest first by default. Returns print-ready URLs usable in edit_document operations (replaceImage or addImage). There is no keyword search — filter by date range or recency only.

  • remove_asset_backgroundActs

    Remove the background from an existing Sherbert asset (assetId from upload_asset), returning a linked, ready-to-use transparent variant. Processing can be asynchronous — a `processing` status is not an error; retry this same tool after `retryAfterMs`.

  • create_documentActs

    Create a design document for a product — the single source of panel IDs, dimensions, and sections for that product/options combination. The response's panels include each panel's id/name/width/height, text/image placeholders and purposes, and semantic section data, useful for sizing and targeting artwork in external design tools before editing. The top-level url is the exact Studio handoff link; present it without modifying, truncating, re-encoding, or routing it through a search engine or third-party redirector. previews holds one image per printable side of this design; preview URLs are opaque, so never construct or edit one; after edits, call get_document or render_preview for current ones. A panel with printable: false won't print in this configuration; designing it needs a configuration that prints that side via refine_product_selections, then a new create_document call. Two modes: (A) provide a templateToken from search_templates to start from a template, or (B) omit templateToken to get a blank full-bleed document with placeholder images. edit_document customises text, style, and images using operations against these panel IDs; render_preview and add_to_cart operate on the resulting workId.

  • add_to_cartDestructive

    Add a designed product to the user's VistaPrint shopping cart. The design is identified by its workId: the cart gets the work's latest saved design, including every edit_document change. The latest create_document, edit_document, or get_document response suggests complete add_to_cart args in next_suggested_actions. For a selected multi-item get_order response with a workId for every item, call add_to_cart separately for each order item to add the whole order. For a sized product (apparel, bags, pens, drinkware, caps), pass Size in options — add_to_cart updates the existing cart entry for that design rather than adding a duplicate, and when the work already has several saved sizes, those saved sizes are authoritative over whatever Size is passed here. Returns the direct cart handoff in the top-level url field. When presenting the checkout link, use that exact url without modifying, truncating, re-encoding, or routing it through a search engine or third-party redirector. Subsequent edits via edit_document automatically update this cart item.

  • get_orderRead-only

    List a signed-in customer’s recent VistaPrint orders or read one order by its displayed order number. Requires the storefront locale. Without orderNumber, the tool lists recent orders. The page defaults to 0 and accepts a returned nextPage for more orders. With orderNumber, the tool reads one order, and page cannot be used. Reports storefront-localized item states by quantity, total paid, available dates and shipment links, and the order-details URL. totalPaid is already formatted for the requested locale; present it exactly as returned. merchantProductKey, merchantProductVersion, merchantProductAttributes, and workId are internal reorder arguments: never show them to the customer in chat. If every item has complete reorder details including workId, and the customer requests a reorder, call add_to_cart once for each item. Share the cart link after all items succeed.

  • list_projectsRead-only

    List the user's saved designs from their VistaPrint account (My Projects), newest first — the source for reprinting, editing, or reordering a past design. Returns up to 9 projects; narrow with name (matches part of the project name) or productKey when the user has described the design they mean. When hasMore is true, repeat the call with the same filters and offset set to nextOffset for the next page. Each project has a workId usable with get_document or edit_document. Each project's url is the exact Studio handoff link; present it without modifying, truncating, re-encoding, or routing it through a search engine or third-party redirector.

  • get_documentRead-only

    Retrieve a summary of a Work entity's design — text fields, images, shapes (with style, rotation, and z-index), and previews (one ready-made image per printable side, labelled e.g. Front/Back, for the current document revision). Preview URLs are opaque: present them exactly as returned and never construct or edit one; call get_document or render_preview for current ones. Does NOT return raw CimDoc.

  • edit_documentDestructive

    Edit a design document using a sequence of operations. Supports: editText (change text content), editTextStyle (change font, size, color, alignment), replaceImage (swap image URL), addText (add new text area), addImage (add new image), move (reposition/resize), reorder (change z-index), remove (delete element). Use the panel summary from create_document or get_document to see current field IDs. Operations execute in order. If this design is in the cart, the correlated cart item is updated automatically; add_to_cart uses the latest saved design for this workId. The response previews are per-side images of the edited design; present them unchanged and never construct or edit one. The top-level url is the Studio link. render_preview reflects the result on the product.

  • render_previewRead-only

    Render an interactive product preview (3D where available, plus 2D scenes and flat per-side views) of a design on its product, using the workId from create_document. The interactive preview shows the user every available view. The response has previews, one flat image per printable side labelled by name (e.g. Front, Back), and a top-level url for the 2D product scene, all for the current document revision. Preview URLs are opaque: present them exactly as returned and never build or edit one. A side that is not in previews has no preview; say so rather than constructing a URL. After edits, call render_preview again for current URLs.

Read from the server on 2026-11-17, including each tool's own safety annotations.

Limits

  • Availability is contested. VistaPrint's guide, last updated 21 Oct 2026, says the connector is not yet available in Claude, while Anthropic's 2026-11-17 directory snapshot lists it and the endpoint answers. Check your own connector list.
  • No checkout in chat. VistaPrint states checkout always happens on its website. The connector ends at a cart link.
  • The guide and the server disagree on uploads. The guide says Claude users add their own images through a public image link only. The live server also exposes begin_asset_upload and show_asset_upload_picker for files attached to the chat, which the guide does not mention.
  • get_order is undocumented. The guide lists no order-reading tool; the live server has one.
  • Some products have no templates. search_templates works only for products with a template gallery; the rest need your own artwork.
  • Image links must be public. upload_asset fetches from a public HTTPS URL.
  • Your cart can change. add_to_cart and edit_document are annotated destructive and act on your real VistaPrint cart and saved designs.
  • Prices are advisory. get_price is display-only; the cart and checkout set the final price.

Frequently asked questions

Can I place or pay for a VistaPrint order in Claude?

No. VistaPrint's connector guide states that checkout always happens on VistaPrint, so you cannot place an order or pay inside the chat. The connector's last step adds your finished design to your VistaPrint cart and gives you a cart link. You review the order, enter payment and confirm it on the VistaPrint website, outside the conversation with the assistant.

Why isn't Claude using VistaPrint when I ask?

Check that the VistaPrint toggle is on for that chat. VistaPrint's guide says to select the plus button in the chat box, open Connectors and make sure VistaPrint is switched on. If the problem continues, disconnect VistaPrint, connect it again and sign in. If it still fails, contact VistaPrint support through its Help Center with the assistant name, your device type and any error message.

How do I link a different VistaPrint account to Claude?

Disconnect VistaPrint, then reconnect from a private browser window. VistaPrint's guide explains that the assistant otherwise links your previous VistaPrint account automatically. In the private window, sign in to Claude, connect VistaPrint again and sign in with the other VistaPrint account. Disconnecting is under Settings, then Connectors, then the Yours tab, where you select VistaPrint and choose Disconnect.

Sources

Use it in an agent

Put VistaPrint to work.

Connect VistaPrint once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.