The assistant connection is in private beta for invited UK accounts. The current pilot supports existing artwork, saved card drafts and fixed print proofs. Live assistant ordering is disabled while supplier checks are completed. Public directory listings are being prepared; an app-store listing is not available yet.

MCP server URL: https://sillyrobotcards-assistants-hfffi.ondigitalocean.app/mcp

Contact us about the pilot. You can also make a card on the website today.

See the synthetic reviewer results walkthrough.

Use https://sillyrobotcards-assistants-hfffi.ondigitalocean.app/mcp with an invited UK account. The server uses Streamable HTTP, OAuth authorization-code flow with S256 PKCE, resource binding, discovery and dynamic client registration. An unauthenticated request advertises protected-resource metadata. Follow its authorization-server metadata; do not substitute an account JWT or send a Stripe key.

Initialize MCP, then use tools/list for current input/output schemas and tool annotations. A listed tool can be unavailable until its pilot feature is enabled. Handle an insufficient-scope challenge through ordinary user consent and stop when access is denied.

Try the public synthetic sample artwork with a square card. Save it to your own account through the ordinary upload flow before importing it. This sample contains no customer artwork.

get_allowance needs profile:read; list_assets and get_asset need assets:read; get_job needs jobs:read. list_products needs the base mcp scope.

import_asset needs assets:read/write. Draft tools are create_print_draft, get_print_draft and update_print_draft, with assets:read and the relevant drafts:read/write permissions. prepare_print_proof and get_print_proof require the relevant drafts/proofs permissions advertised by each tool.

get_quote needs drafts:read and proofs:read. prepare_order also needs orders:write. get_order needs orders:read and omits recipient details and Stripe payment URLs. Every tool requires the mcp scope and current account authorization.

1. Import exactly the image the user selected. Save a supported draft and read its current revision.
2. Prepare a proof bound to that revision. Read its five fixed pages; do not describe an ordinary chat image as print approval.
3. Get a current quote for the proof, country and quantity. Quotes expire within five minutes; preparation refreshes prices.
4. After the user chooses delivery, prepare one order with the exact proof, expected total, recipient and stable operation key. On uncertainty, stop; retry only the original key with identical input. Changing price or artwork under the same key is refused.
5. Return the website review link. The user checks all pages, delivery and the final total and approves before Stripe Checkout. Never infer payment or shipment from preparation success.
6. Read the recorded order status. Unknown or foreign resources receive a generic refusal. Preserve cancelled, refunded and expired states; do not create a replacement charge to recover them.

Keep private signed URLs, addresses, messages and OAuth credentials out of public examples, logs and shared documents. The connector provides no pay, refund, supplier-dispatch or generation tool.

Report unclear payment or fulfilment outcomes through Silly Robot support. Include the order ID privately and reuse its existing review link. Directory availability is separate from protocol compatibility; private QA success does not mean a store has accepted the app.

Sign in directly to Silly Robot Cards and review the app name, callback and each requested permission. Connections expire after 30 days and can be revoked in connected apps. Reconnecting may ask for individual permissions again.

The assistant receives only the account data needed for the tools you approve. Depending on the permission, that can include allowance, selected private images, job status, drafts and inside messages, proof previews or order status. Image and proof links are private and short lived; keep them out of public posts.

For an enabled order, your chosen delivery details are saved in Silly Robot Cards. You review the fixed design, delivery and final total on our website, then pay in Stripe Checkout. Fulfilment uses Prodigi after payment and order checks. The connector has no tool to pay, approve print, refund, cancel fulfilment, generate new artwork or spend image allowance.

Read our privacy policy, terms and refunds and returns policy. The host app also applies its own chat and data settings.

If access expires or you disconnect, reconnect through the app and approve the permission you need. If a proof cannot load, use Refresh proof on the saved review page. If payment is interrupted, reopen the same review link and check its status before paying again. Contact support if the payment status remains unclear.

Replaying an order request must use its original operation key and unchanged details. An expired, changed or refunded order must not be reopened as a new payment. Disconnecting an app does not cancel an order already paid for; use the website and support for order help.