For teams

Assistants for teams

A Printonic for Teams account gets a different set of tools on the same hosted server: no listings, no publishing, no keys to manage. An assistant browses the collections, quotes a team order and files it. A person approves it.

Which tools you get

The server decides per sign-in. A member of a team (owner, approver or requester), or an account in teams mode, sees the printonic_teams_* tools below and nothing else. Every other account sees the seller tools. Tools act on the team’s account (the owner’s), never on the member’s own.

Tool	Class	What it does
`printonic_teams_list_collections`	Read	The gift kits and event kits, priced from the live catalog.
`printonic_teams_quote_team_order`	Read	Every recipient priced as its own shipment; event fees; rows with problems. Creates no order.
`printonic_teams_create_team_order`	Team order	Files the order (unpaid) and holds it in the team approvals tray. Never pays. Idempotent per key.
`printonic_teams_list_team_orders`	Read	The team's orders with state, totals and the latest approval.
`printonic_teams_get_team_order`	Read	One order: recipients, claimed / shipped / delivered counts, on-time summary, approval state. No recipient links or emails.
`printonic_teams_list_pending_approvals`	Read	What is waiting for an approver, with the review URL.
`printonic_teams_send_gift`	Prepare	Prepare one gift for each of 1–50 typed recipients, CRM contacts or roster people. Use exactly one gift collection_slug, item_slug or owned items array. A roster recipient requires an approver identity; this does not grant payment authority. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_get_gift`	Read	Read a gift and its lifecycle, shipment tracking and approval status using its returned gift ID. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_search_contacts`	Read	Search the team's connected HubSpot or Salesforce account; returns IDs and public contact descriptors for use with send_gift. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_list_people`	Read	Read the employee roster. Only owner/approver identities with people:read can access roster data. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_upcoming_dates`	Read	Read upcoming birthdays and work anniversaries in the team's roster. Dates use the existing Pacific calendar rules; requires roster access. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_list_templates`	Read	Read the team's saved gift setups; reuse checks current products and artwork. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_use_template`	Read	Load a saved template as a fresh draft with current availability checks and warnings. Returns a draft requiring new recipients; creates no paid order. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_create_large_campaign`	Prepare	Prepare one gift bundle for up to 5,000 named recipients in controlled batches. Human approval and team balance are required before batches can be paid; this tool cannot approve or process payments. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_get_large_campaign`	Read	Read a large campaign's batch progress, pauses, approval requirements and totals. Completed batches are paid, not necessarily delivered. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_list_rules`	Read	Read existing HR or CRM gift rules. Does not enable, evaluate or send from a rule. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_add_artwork`	Prepare	Import an image from a public HTTPS URL into the team's artwork library. The existing image validation and private-network restrictions apply. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_preview_artwork`	Prepare	First pass product_id alone to discover print areas. Pass product_id, placements and idempotency_key to request a preview. Then pass preview_id to read progress and actual render URLs when ready. Placements map print-area IDs to artwork_id (or 'logo') and contain/cover fit; an unrendered job is never presented as a finished mockup. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_get_proof`	Read	Read actual campaign print proofs, versions, comments and review state. The assistant cannot sign a proof or release its production hold. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_get_balance`	Read	Read posted team cash and credit balances. Requires an owner/approver identity and billing:read; does not fund or authorize spending. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_list_invoices`	Read	Read the team's invoice ledger, amounts and payment state. Requires billing access. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.
`printonic_teams_get_statement`	Read	Read a monthly finance statement as structured data. Requires billing access. Assistant actions never approve, fund or pay. Orders wait for a signed-in human approver. Recipient emails and claim links are never returned.

The approval rule

An assistant never pays. Every team order it files is created with its shipments unpaid and held in the team’s approvals tray, owners included. The tray shows who asked (“Claude via jane@acme.com”) and the order preview. An owner or approver approves it in Printonic; approving pays from the team balance and sends the order to production. Requests expire after 7 days.

A live REST integration can receive an explicit owner-granted payment scope with spending caps. MCP does not use that grant or the older assistant auto-approval setting: its new orders always wait for a person. See the Teams API reference for the separate REST payment rules.

A held call returns held_for_approval: true, a request_id, the review_url and the order summary. Poll printonic_teams_get_team_order with the campaign_id for the outcome; never file the same order twice. Repeat the same idempotency_key to retry safely.

Connecting

The server address is https://platform.printonic.com/mcp, the same for everyone.

In claude.ai, Claude Desktop or the ChatGPT app, add a custom connector with that address and sign in with the email of your Printonic account. No code is pasted; the connection acts for your team.

Cursor, Claude Code and the OpenAI API connect with a personal access code created on Dashboard, Assistants. It is a psa_live_ credential tied to you; the team it acts for is the one you belong to.

claude mcp add --transport http printonic https://platform.printonic.com/mcp \
  --header "Authorization: Bearer <access code>"

You can also use a scoped ptk_live_ or ptk_test_ service-account key from Integrations, API keys. That key is pinned to its team and can access only its granted scopes. Test keys use an isolated sandbox.

Example prompts

Recipients, kits and options

Recipients with emails get a link to enter their own address; recipients with full addresses are shipped directly; a headcount opens that many shared-link seats. Up to 100 recipients per team order.
Destinations: US plus CA, GB, AU, DE, FR, NL, IT and ES. Each recipient is priced at their country’s rate; duties on international parcels are paid by the recipient on delivery.
Kits come from the Teams catalog (the same kits shown on /teams and /teams/events; the slugs are the kit slugs there). Their items are prepared once on the team account, with the team logo when one is set.
Variations (size, color): every collection line carries the catalog’s rule per group, listed by printonic_teams_list_collections as recipients_choose and buyer_chooses (and per line as recipient_chooses, buyer_chooses, fixed_summary). A fixed group is locked to the catalog’s option and cannot be changed through options. A recipient group is picked on the recipient’s link (nothing is made until they do); with supplied addresses there is no link, so the first available option is assumed and reported back as assumed_options. A buyer group is assumed and reported the same way so you can pass options to change it; a group with no rule behaves like a recipient group.
add_ons.printed_card puts a folded card with the gift message in every parcel. event carries the event date, rush and kit assembly; the fees are server-priced.
Bulk delivery of an event kit to one venue is a dashboard order for now; through an assistant every attendee is shipped their own parcel.

Limits

Team tools share the per-minute limit of the credential that made the call: an access code carries the limit stamped on it, a sign-in gets its plan’s (30/min free, 120/min Pro). Every call is audit-logged. Artwork previews use the same rendering limits as the Teams dashboard. The same per-account suspension switch applies to team principals; service-account keys also honor the team API switch and their individual rate limits.

What the tools never return

Recipient claim links (the only credential a recipient has) and recipient emails.
Anything from another team, another member’s own account, or the seller side of the platform.
Approval credentials, funding secrets or a payment caused by an assistant call. Read tools can show an order that a person already paid.

Teams REST API Seller docs Clients Help guide Printonic for Teams