Connect to your own platform
MCP (Model Context Protocol) lets an assistant use HeyMadeIt tools with your permission. For HeyMadeIt accounts use https://heymadeit.com/mcp. For a printer platform use https://YOUR-PRINTER-HOST/mcp and sign in with that platform’s account. Use OAuth in clients that support it, or the access token method shown in Design with AI. A merchant REST API key is not an MCP token. Never paste credentials into a design brief.
Confirm the account and workspace
Start with whoami. Check the account and available teams, and explicitly choose the intended company space. If the wrong account appears, disconnect and reconnect on the correct hostname. Tool visibility follows your role; the assistant does not gain administrator rights.
Create a design with an assistant
Ask the assistant to search_templates, inspect get_template, and use create_from_template for your chosen template. It can change text and images, manage pages and folders, use your brand kit, and run check_design. Review its preview and open the returned editor_url exactly as supplied. export_design and get_export prepare and retrieve supported downloads. Plans and print preflight still apply.
Create an A5 flyer in our company team using our brand kit. Find a suitable template, insert the text I supply, show me a preview, and fix any check_design findings. Leave missing dates and prices as placeholders.Publish a printer template
Printer owners, administrators and designers with template management permission get template_kit_info, check_template, publish_template and template_import_status. Read the kit and schema, write a complete TemplateSpec with Danish and English text, check it, inspect previews and fix all errors and warnings. Publish only after the user requests publication. Check and publish are separate calls.
On this printer platform, create an A5 template for our customers. Read template_kit_info overview, schema, formats, palettes and fonts. Use local slug summer-offer. Run check_template and show me the previews. Wait for my publication instruction before calling publish_template.Ownership and customer visibility
On your printer host, publishing always targets your printer. The server prefixes the local slug with p followed by your tenant number; keep the local slug short enough for the final slug’s 64-character limit. Reuse your original local slug to update your own template. Do not send the generated prefix back as the local slug. Published templates appear in that printer’s catalogue and template API for customers to copy. They do not enter HeyMadeIt’s shared catalogue or another printer’s platform. Printer templates are visible to all customers of that printer; this is not a private template per client company.
Wait for the result
A render may outlast one MCP call. If the response includes run_id and queued or running status, call template_import_status with that run_id after the suggested delay. Publication is confirmed only when outcome is published and the returned format statuses are published. Keep the returned public_urls and test them on your printer hostname. A queued run or clean check is not publication.
Access and troubleshooting
If publishing tools are missing, confirm the printer hostname, staff role and template permission, then refresh the client’s tool list. Customers can edit their own designs but cannot publish templates. A revoked user permission is checked again when queued publication runs. For rejected JSON, read the exact schema and feedback rather than retrying unchanged content. Disconnect or revoke the assistant token when access is no longer needed.