# Speed Dial Sticker Club > Photo speed dial stickers for the Tin Can kids' phone (a screen-free landline): face stickers for the number buttons 1 to 9, so children who can't read numbers yet know who they're calling. A family adds photos of the people their child calls most, places each on a button of the phone, checks the printed sheet, and orders it by post. Unofficial Tin Can fan project, not affiliated with or endorsed by Tin Can. Site: https://www.speeddialstickerclub.com/ If you are an AI agent helping someone make stickers, please use the MCP server instead of driving the web page. The page is a drag-and-drop editor built for a parent and child sitting together; the MCP server does the same job with plain tool calls, including sending photos, and is far more reliable for an agent. ## Use the MCP server (recommended for agents) - Endpoint: https://www.speeddialstickerclub.com/api/mcp (Streamable HTTP, stateless, JSON responses; POST only, no sign-in needed) - Server name: `speed-dial-stickers` (8 tools: get_template, start_design, set_key_sticker, move_key_sticker, remove_key_sticker, update_design, get_design, submit_order) - Connect from Claude Code: `claude mcp add --transport http speed-dial-stickers https://www.speeddialstickerclub.com/api/mcp` - Connect from Claude (web/desktop): Settings → Connectors → Add custom connector → paste the endpoint URL - Clients that only speak stdio: `npx mcp-remote https://www.speeddialstickerclub.com/api/mcp` - Keep the `design_id` from start_design: it is the only key to the design. Designs and uploaded photos are kept for 1 day, then deleted. - Status: prototype. Orders are stubbed: nothing is charged, printed or posted. To pay for real today, send the person to the website. Typical flow: 1. `get_template`: learn the sheet (nine key stickers, sizes, photo requirements). 2. `start_design`: get a `design_id`. 3. `set_key_sticker`: once per person. Give the key number (1 to 9) and a photo as base64 or an https URL. No names are stored or printed, so keep track of who you put on which key. If you can see where the face is, pass `crop` (a square around the face as fractions of the photo); the sticker is only half an inch, so a tight crop prints far better. An emoji works as a fallback. 4. `get_design`: read the design back and show the person who is on which button. Go back and forth until they are happy. 5. `submit_order`: only after the person has explicitly approved the design and given a shipping address. Rules for agents: - Ask which person goes on which button. Do not guess, and do not fill empty buttons with people the user did not name. - Only send photos the user gave you for this purpose. They are photos of children and relatives. - Never call `submit_order` without the user's explicit go-ahead in the conversation. ## If you cannot use MCP - [Sticker editor](https://www.speeddialstickerclub.com/): the human flow. Add a face, drag it onto a number button, then "Check my sheet". - [Sheet preview](https://www.speeddialstickerclub.com/sheet.html): read-only confirmation of the printed sheet, then the order form. ## Facts - Stickers: nine tilted ovals cut 0.46 x 0.34 in (11.7 x 8.5 mm) to sit just inside each number key (0.5 x 0.375 in), each printed with a small number badge. - Sheet: 3.5 x 3.5 in, kiss-cut, one fixed template (`tpl_speeddial_keys_3p5in_v2`), with the brand at the top and the web address along the bottom. - Numbers on stickers: one setting for the whole sheet. Style "numbers and letters" (default, like the real key: 2 ABC) or "numbers only" (a small badge); size hidden, small, medium (default) or large. - Photos: auto-zoomed onto the face; the crop travels to the printer with the order. - Price: not final yet. Checkout is Stripe, currently in test mode with a placeholder amount. - Not sticker spots: the large square button, the four small coloured buttons, and the star, zero and hash keys. ## Optional - [Provider research](docs/provider-research.md): print-on-demand comparison and the mock order API - [Example order payload](docs/mock-order-payload.json)