⭐ 20% OFF when you set 3 birthday reminders
⭐ Never miss a birthday again · Set 3 reminders and get 20% off your next card · Set reminders
Personal cards · UK and US

Silly Robot Cards MCP reference

Connect a compatible assistant through account consent, preserve fixed proofs and use the website for print approval and payment.

Availability

Make a real printed card from a picture you already have, posted to an address in the UK or the US. No account is needed: when you post it, give an email or sign in with Google, Facebook or Apple. Signing in is optional and lets you reuse saved pictures. You check the card, delivery and total on our website and pay in Stripe Checkout. The connector never generates artwork.

Production MCP URL: https://mcp.sillyrobotcards.com/mcp

This is our production assistant service on the Silly Robot Cards domain. Use this URL when adding your connection.

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

See the recorded card-preview walkthrough.

Connection and discovery

Use https://mcp.sillyrobotcards.com/mcp. make_card and change_card work without an account: they advertise noauth alongside oauth2. Every other tool needs a signed-in Silly Robot account. Cards can be posted to UK and US addresses. 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. Some listed tools stay unavailable until their feature is enabled for an account. 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. Pass its URL to make_card as image.download_url; no account is needed. This sample contains no customer artwork.

Card tools

make_card turns one picture (a public HTTPS image URL passed as image.download_url, or a picture_id from my_cards) into a square or 5 × 7 inch portrait greeting card with up to three inside messages: sweet, cheeky and savage. It saves the picture and draft and prepares the print proof in one call. A retry with the same input returns the same card. change_card switches the tone, replaces the words or changes the shape, and saves a new version rather than overwriting. Without signing in, make_card also returns a claim; pass it to change_card to edit that card. On the post_url page, a guest gives an email, or signs in with Google, Facebook or Apple, before checkout. Unclaimed guest cards are deleted after 30 days. my_cards and picture_id need a signed-in account. my_cards lists the account's saved card pictures. make_card and change_card return a short text summary and structured content with the card's format, inside message, price (£3.99 in the UK, $4.99 in the US, plus delivery) and post_url, the website page where the customer reviews the card, delivery address and total and pays in Stripe Checkout. The connector does not generate artwork or spend image allowance.

Read and write classification

Read (no side effects): my_cards, get_allowance, list_assets, get_asset, get_job, list_products, get_print_draft, get_print_proof, get_print_proof_status, get_quote, get_order.

Write, not sensitive (saves pictures, drafts or proofs in the customer's own account; nothing is charged, sent or published): make_card, change_card, import_asset, create_print_draft, update_print_draft, prepare_print_proof, reserve_print_proof, start_print_proof. prepare_order creates an unpaid order and a website review link; it never charges.

Sensitive write: none today. No tool charges, refunds, sends mail or dispatches a card; payment always happens on the website. Write tools take a stable operation key and refuse changed input under the same key, so retries cannot create duplicates. Errors return a short code and message, for example PRICE_CHANGED, PROOF_CHANGED or ORDER_LIMIT; an expired connection returns an OAuth invalid_token challenge.

Tools and permission boundaries

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. These three order tools are not enabled and return an unavailable error; customers order through post_url instead. Every tool requires the mcp scope and current account authorization.

Status notifications pilot

MCP Events are opt-in and enabled only for the invited private pilot; public notification availability is not yet verified. When enabled, modern MCP discovery advertises events support; use events/list for the current definitions. OpenAI supports these events in ChatGPT Work on the web, desktop Work with Cloud selected, and dots. Ordinary ChatGPT chat, Claude and Codex require separate compatibility checks. See the OpenAI events reference.

Subscribe to one owned proof with print_proof.ready or print_proof.failed, or one owned order with card_order.status_changed. Notifications require events:subscribe and the corresponding proofs:read or orders:read permission through account consent. The server verifies the HTTPS callback before saving a subscription and signs deliveries with Standard Webhooks. Notification data contains only the resource ID, recorded status and, for orders, the account website link.

When the async proof pilot is enabled, call reserve_print_proof with the current draft revision and a stable request key. It returns a proof ID without rendering. When advertised, call prepare_print_proof_monitoring for that owned ID and the chosen ready or failed event to request drafts:read, proofs:read and events:subscribe through ordinary consent. It reads only proof status and returns the exact event filter; it does not create a subscription. Then subscribe to that ID before start_print_proof queues the render, then use get_print_proof_status for current state and get_print_proof for the ready pages. Reservation and start require assets:read, drafts:read and proofs:write; status requires drafts:read and proofs:read. The existing prepare_print_proof remains supported and returns after rendering, so its first completion cannot be monitored by subscribing afterward.

Subscriptions expire within 24 hours, end when access is revoked, and must be refreshed before their returned deadline. Delivery can be duplicated or arrive out of order; read the resource for its current state. There is no event replay: recover missed updates with the ordinary read tools. These events observe saved Silly Robot resources; they do not observe image generation inside an assistant. A status update cannot approve a proof, place an order or pay.

Safe order sequence

Customers order today through post_url (Post it) on the website. The order tools in steps 3 to 6 are not enabled yet; this is how they will behave when they are.

  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.

Support and disclosures

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.

Your account, your choices

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.

When you post a card, your delivery details are saved in Silly Robot Cards. You review the card, delivery and final total on our website, then pay in Stripe Checkout. After payment, cards are printed and posted by Prodigi in the UK and Gooten in the US. 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 something interrupts the flow

If access expires or you disconnect, reconnect through the app and approve only the permission you need. If only a private preview link has expired and your saved proof is still valid, ask the assistant to reopen it for fresh preview links. You do not need to create a new card or render that proof again. If you have a website order-review link, use Refresh proof there when an image cannot load.

For an enabled order, keep the same review link if payment is interrupted and check its status before paying again. Ask the assistant to resume the existing order; an expired, changed or refunded order needs the appropriate website or support recovery. Disconnecting an app does not cancel an order already paid for. Contact support if the payment status remains unclear.

All assistant guides · Developer reference

logo

Silly Robot Cards

Ridiculous cards. Real laughs. Made personal with AI.

Assistant connection guides

TwitterFacebookInstagramTikTok
Get the app

Explore

Operated by Gleeboard Ltd

© 2026 Silly Robot Cards. All rights reserved