Search / io.mydesigns/mcp
protogridR0· no sign-inCreate print-on-demand products, publish them to your MyDesigns store, and track sales.
v1.0.1 · active · website · descriptor JSON · versions
{
"mcpServers": {
"mydesigns": {
"type": "http",
"url": "https://mcp.mydesigns.io/mcp"
}
}
}claude mcp add --transport http mydesigns https://mcp.mydesigns.io/mcp[mcp_servers.mydesigns]
url = "https://mcp.mydesigns.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mydesigns": {
"type": "remote",
"url": "https://mcp.mydesigns.io/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"mydesigns": {
"type": "http",
"url": "https://mcp.mydesigns.io/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=mydesigns&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLm15ZGVzaWducy5pby9tY3AifQ%3D%3D"
}{
"servers": {
"mydesigns": {
"type": "http",
"url": "https://mcp.mydesigns.io/mcp"
}
}
}{
"mcpServers": {
"mydesigns": {
"httpUrl": "https://mcp.mydesigns.io/mcp"
}
}
}extensions:
"mydesigns":
enabled: true
name: "mydesigns"
type: streamable_http
uri: "https://mcp.mydesigns.io/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every useauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length2 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations36 of 36 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 9,915 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes, stability.rug_pulltool history recorded for 3 of the 7 days neededdeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageupload_designschangeddescriptionOpen a card where the seller uploads their own images (PNG or JPEG, up to 20 MB each) as designs. Use it when the seller wants products from art they already have: you cannot take an image from the chat, and never write a prompt to recreate one. The card saves the files and then gives you their designIds, which create_products takes instead of a prompt, at no credit cost. Uploading costs nothing.
Open a card where the seller uploads their own images (PNG or JPEG, up to 20 MB each) as designs. Use it when the seller wants products from art they already have: you cannot take an image from the chat, and never write a prompt to recreate one. The card saves the files and then gives you their designIds, which create_products takes. Uploading costs nothing.
get_design_statusaddedWait for the designs a create_designs call is making, by the jobId it returned, and get their designIds. It waits up to about 40 seconds for them to finish. CREATING: still being made; call it again. READY: all made. FAILED: done, but some or all were not made; problems says why, and the designs that were made can still be used. NOT_FOUND: no such design job for this seller. When the seller asked for products, call create_products with the designIds as soon as this says READY or FAILED, without waiting for the seller.
create_designschangeddescription, output schemaCreate designs, the app's Dream AI: make 1 to 10 designs for the seller with AI, one per prompt, and save them in their MyDesigns designs. No product is made. When the seller asks for Dream AI or the dreamer, or to dream designs, use this tool. Use it too when the seller wants designs only, or wants to see the designs before choosing products; when they want products, create_products makes the designs and the products in one call. Plan exactly as many designs as the seller asked for, each with its own idea; for more than 10, call again with the rest. The designs are generated together, about 1.5 AI credits each on the default model (other models cost more or less), and take up to a minute or two. Before designs the seller did not clearly ask for (redos, more versions, a vague "make them pop"), tell them they cost credits and wait for a yes. A design that could not be made is listed with the reason and the others are still made. A card shows the seller the designs, so do not put the images in your reply. To make products from them later, give create_products their designIds, never their prompts again: a prompt makes a new design and costs credits again.
Create designs, the app's Dream AI: start making 1 to 10 designs for the seller with AI, one per prompt, saved in their MyDesigns designs. No product is made. When the seller asks for Dream AI or the dreamer, or to dream designs, use this tool. It is also the first step when they want products with new designs: products are made only from designIds, so make the designs here, then give their designIds to create_products. Plan exactly as many designs as the seller asked for, each with its own idea; for more than 10, call again with the rest. About 1.5 AI credits each on the default model (other models cost more or less). Before designs the seller did not clearly ask for (redos, more versions, a vague "make them pop"), tell them they cost credits and wait for a yes. The designs are made in the background, usually within a minute: this returns a jobId at once, and a card shows the seller each design with its picture as it finishes, so the reply needs no list or pictures of its own. Then call get_design_status with the jobId; it waits for the designs and gives their designIds.
design_creation_progressaddedHow far a design job has got. The designs card calls this while it is open.
product_creation_progresschangedoutput schemaget_product_statuschangeddescriptionCheck whether products started with create_products are made yet, or products sent with publish_products are in the store yet, by the jobId each call returned. CREATING: still being made or published, which usually takes a few minutes; check again later, not over and over. READY: all made (or all in the store). FAILED: done, but some or all were not made; the failed list gives each one's designId and the reason, and the design is kept, so it can be tried again with that designId. NOT_FOUND: no such product job for this seller, or one started only seconds ago.
Check whether products started with create_products are made yet, or products sent with publish_products are in the store yet, by the jobId each call returned. CREATING: still being made or published, which usually takes a few minutes; check again later, not over and over. READY: all made (or all in the store). FAILED: done, but some or all were not made; the failed list gives each one's designId and the reason, and the design is kept, so it can be tried again with that designId. NOT_FOUND: no such product job for this seller, or one started only seconds ago. Each product made so far comes with its main mockup and a link that opens it in the MyDesigns app, and productsLink opens all of them: give the seller the link when they are ready, so they can find them in the app.
create_productschangeddescription, input schema, output schemaCreate 1 to 10 print-on-demand products for the seller, one per design: generate each design from a prompt with AI (or use an existing design), then make them into products with one of the seller's product profiles, which sets the products, colors, sizes, prices and mockups. Find the profile with list_profiles first: when the seller named a product (a tee, a Gildan 5000, a mug), search for it and use a profile only if it clearly fits. When the seller named no product, or nothing fits, show them a few profiles and ask which to use; never pick one for them. Plan exactly as many products as the seller asked for, each with its own design idea, and count them before calling; for more than 10, call again with the rest. The designs are generated together, about 1.5 AI credits each (a reused designId costs none), and take up to a minute or two. Before new designs the seller did not clearly ask for (redos, more versions, a vague "make them pop"), tell them they cost credits and wait for a yes. A design that could not be made is listed with the reason and the others still go ahead. The products are saved together in the seller's MyDesigns products, not put in any store; they are not drafts. They are then made in the background over a few minutes: check them with get_product_status and the one jobId returned here, and tell the seller when they are ready. Show the seller the design images.
Create 1 to 10 print-on-demand products for the seller, one per design they already have, with one of the seller's product profiles, which sets the products, colors, sizes, prices and mockups. Every product needs a designId: from create_designs once get_design_status gives it, an upload, deep search or list_designs. For a product with a new design, call create_designs first, wait for it with get_design_status, then call this with the designIds, all in the same turn. Find the profile with list_profiles first: when the seller named a product (a tee, a Gildan 5000, a mug), search for it and use a profile only if it clearly fits. When the seller named no product, or nothing fits, show them a few profiles and ask which to use; never pick one for them. Plan exactly as many products as the seller asked for, and count them before calling; for more than 10, call again with the rest. The designs cost no AI credits here; a profile with AI video mockups still costs credits for each video. The products are saved together in the seller's MyDesigns products, not put in any store; they are not drafts. They are then made in the background over a few minutes: check them with get_product_status and the one jobId returned here, and tell the seller when they are ready. A card shows the seller each product with its picture and its progress as it changes, so the reply needs no list, pictures or status of its own.
get_deep_search_resultschangeddescriptionThe designs a deep_search_designs run has made, by its jobId. RUNNING: still researching or designing, which usually takes a few minutes; the designs so far are listed; check again later, not over and over. DONE: all made. A card shows the seller each design's image and title, so do not put the images in your reply. The titles are long, search-friendly ones: shorten them for create_products if the seller wants. A design on trademarkHold has text a trademark check flagged; tell the seller before they sell it. Problems say why a niche found nothing or a design was skipped. NOT_FOUND: no deep search by that id for this seller.
The designs a deep_search_designs run has made, by its jobId. RUNNING: still researching or designing, which usually takes a few minutes; the designs so far are listed; check again later, not over and over. DONE: all made. A card shows the seller each design's image and title, so the reply needs no pictures of its own. The titles are long, search-friendly ones: shorten them for create_products if the seller wants. A design on trademarkHold has text a trademark check flagged; tell the seller before they sell it. Problems say why a niche found nothing or a design was skipped. NOT_FOUND: no deep search by that id for this seller.
create_designschangedinput schemasave_store_imagechangedannotationsShowing the latest 10. Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website +reachable +uptime-100% +updated-3d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://mcp.mydesigns.io/mcp streamable-http | none | yes | 100% | 317 ms | 2026-07-28 | 2026-11-07 |
add_store_domain | Connect a domain the seller already owns to a store; it does not buy one. A root domain (example.com) also adds its www version. Needs a paid plan. The result lists the store's domains with the DNS record to add for each: give the seller those exact values to add where they bought the domain. A domain usually goes live a few minutes to a few hours after the record is added; check it then with check_store_domain. |
check_store_domain | Check again whether a domain is live, after the seller added its DNS record. While it is not live, the result repeats the record to add and any problem found with it. |
create_designs | Create designs, the app's Dream AI: start making 1 to 10 designs for the seller with AI, one per prompt, saved in their MyDesigns designs. No product is made. When the seller asks for Dream AI or the dreamer, or to dream designs, use this tool. It is also the first step when they want products with new designs: products are made only from designIds, so make the designs here, then give their designIds to create_products. Plan exactly as many designs as the seller asked for, each with its own idea; for more than 10, call again with the rest. About 1.5 AI credits each on the default model (other models cost more or less). Before designs the seller did not clearly ask for (redos, more versions, a vague "make them pop"), tell them they cost credits and wait for a yes. The designs are made in the background, usually within a minute: this returns a jobId at once, and a card shows the seller each design with its picture as it finishes, so the reply needs no list or pictures of its own. Then call get_design_status with the jobId; it waits for the designs and gives their designIds. |
create_folder | Make a design folder, at the top level or inside another folder. Names must differ from the other folders in the same place; check list_folders first to reuse one that already exists. Then pass its id as folderId to create_products, create_designs or deep_search_designs. |
create_products | Create 1 to 10 print-on-demand products for the seller, one per design they already have, with one of the seller's product profiles, which sets the products, colors, sizes, prices and mockups. Every product needs a designId: from create_designs once get_design_status gives it, an upload, deep search or list_designs. For a product with a new design, call create_designs first, wait for it with get_design_status, then call this with the designIds, all in the same turn. Find the profile with list_profiles first: when the seller named a product (a tee, a Gildan 5000, a mug), search for it and use a profile only if it clearly fits. When the seller named no product, or nothing fits, show them a few profiles and ask which to use; never pick one for them. Plan exactly as many products as the seller asked for, and count them before calling; for more than 10, call again with the rest. The designs cost no AI credits here; a profile with AI video mockups still costs credits for each video. The products are saved together in the seller's MyDesigns products, not put in any store; they are not drafts. They are then made in the background over a few minutes: check them with get_product_status and the one jobId returned here, and tell the seller when they are ready. A card shows the seller each product with its picture and its progress as it changes, so the reply needs no list, pictures or status of its own. |
create_store | Open a new MyDesigns store for the seller. It is live at its link right away but empty: put products in it with publish_products. It can take orders only once it is on a payout account. Check list_stores first: the plan limits how many stores a seller can have, and when the seller has a payout account that is ready, ask whether to use it for this store, naming it by the stores already on it, and on their yes pass it as payoutAccountId; with none ready, the seller sets up payouts in the MyDesigns app. Before calling, tell the seller the name and the web link you will use and wait for their yes: the link cannot be changed later. |
create_store_imagesdestructive | Make images for one of the seller's stores with Dream AI and put them on it: the logo, the banner across the top of the home page, a separate banner for phones, and the favicon (the small icon in the browser tab). MyDesigns picks the model, shape and size each image needs and puts it on the store straight away, in place of the one there; the images are not saved in the seller's designs. A favicon given no prompt is made from the logo in the same call, at no extra cost. It costs AI credits: 1.5 for a logo or a favicon, 3 for a banner or a phone banner. Before calling, tell the seller the cost and which of their current images it replaces, and wait for their yes. When they do not like one image, call again with only that one. Images made elsewhere in this chat cannot be put on the store. Make one call at a time for a store, never several at once. For the seller's own image, use upload_store_image; to take an image off, use update_store. An image with an error in the result was not set: tell the seller. |
deep_search_designs | Deep search, the app's Scout AI: MyDesigns researches what really sells for one or more niches on Amazon right now and makes designs from each, each with a title, description and tags. It is heavy research that takes a few minutes, so do your own research and use create_products by default; offer deep search only when the seller wants to know what sells or wants ideas from real sales data, tell them it uses up to 1.5 AI credits per design, and start it only after they agree. Needs a Pro plan or higher; one deep search runs at a time, so put every search term in one call, one per line: they run as one job, like the Scout AI page. Then check it with get_deep_search_results and the jobId returned here, show the seller the designs, and make products from the ones they pick with create_products and their designIds. |
delete_design_from_carddestructive | Move one design to the seller's trash. The designs card calls this when the seller deletes a design from it. |
delete_designsdestructive | Move designs the seller does not want to their MyDesigns trash, by the designIds create_designs, deep search or an upload gave. Use it only when the seller asked to delete them; when it is not clear which ones they mean, ask. They can restore them from the trash in the MyDesigns app for a while. The AI credits the designs cost are not given back. Never use a deleted designId again, for create_products or anything else. |
design_creation_progressread-only | How far a design job has got. The designs card calls this while it is open. |
get_accountread-only | Get the signed-in MyDesigns account: its id, name, email, subscription plan code (TIER_0 is the free plan) and the subscription that plan comes from: where it is billed (STRIPE, SHOPIFY, PKS, or NONE for the free plan), the plan type (STARTER, PRO, PRO_PLUS), the plan name, status, frequency (MONTHLY, YEARLY, LIFETIME), list price, when it renews or ends, any coupon, and for Stripe the amount the last invoice actually charged after discounts. Fields a billing source does not have are null. aiCredits is how many AI credits the seller has left; new designs spend them. |
get_deep_search_resultsread-only | The designs a deep_search_designs run has made, by its jobId. RUNNING: still researching or designing, which usually takes a few minutes; the designs so far are listed; check again later, not over and over. DONE: all made. A card shows the seller each design's image and title, so the reply needs no pictures of its own. The titles are long, search-friendly ones: shorten them for create_products if the seller wants. A design on trademarkHold has text a trademark check flagged; tell the seller before they sell it. Problems say why a niche found nothing or a design was skipped. NOT_FOUND: no deep search by that id for this seller. |
get_design_statusread-only | Wait for the designs a create_designs call is making, by the jobId it returned, and get their designIds. It waits up to about 40 seconds for them to finish. CREATING: still being made; call it again. READY: all made. FAILED: done, but some or all were not made; problems says why, and the designs that were made can still be used. NOT_FOUND: no such design job for this seller. When the seller asked for products, call create_products with the designIds as soon as this says READY or FAILED, without waiting for the seller. |
get_orderread-only | Get one MyDesigns order by its id: the seller and their shop, the payment method, the billing address, every print partner with its own fulfillment status, created date and tracking, and every line with its partner, SKUs, print areas and manufacturing cost. One order can hold several fulfillments at the same partner, so a partner name is not unique. An admin token reaches any order; any other token reaches only that seller's own orders. userId, userEmail, providerCode and isPrintify are for support staff: when talking to the seller, name the marketplace in words (MyDesigns Store, Etsy) and leave those out. |
get_product_statusread-only | Check whether products started with create_products are made yet, or products sent with publish_products are in the store yet, by the jobId each call returned. CREATING: still being made or published, which usually takes a few minutes; check again later, not over and over. READY: all made (or all in the store). FAILED: done, but some or all were not made; the failed list gives each one's designId and the reason, and the design is kept, so it can be tried again with that designId. NOT_FOUND: no such product job for this seller, or one started only seconds ago. Each product made so far comes with its main mockup and a link that opens it in the MyDesigns app, and productsLink opens all of them: give the seller the link when they are ready, so they can find them in the app. |
get_store_statsread-only | Get a store's real performance over the last N days: orders, items sold, revenue, profit and fees in USD, visits, and its top products, each compared with the N days before. Fees are everything the sales cost the seller: making and shipping the products plus marketplace fees, so call them costs, not fees alone. Top products are ranked by net sales, then by page views; only products with tracked page views are listed, so one that sold without a tracked view is missing from the list. The numbers come from daily rollups, so today's activity can be missing. |
list_designsread-only | List the seller's designs with their folder, title, tags and picture, folder by folder in the order list_folders gives, about 50 at a time. Give folderId for one folder, and search to find designs by title, tags or file name. When nextCursor is set there are more: call again with it and the same folderId and search. A cursor counts designs by place, so after moving or deleting designs it would skip some: start again without it. |
list_foldersread-only | List the seller's design folders with how many designs each holds. parentId is the folder it sits in, null for a top-level one. New designs go in the first top-level folder unless create_products, create_designs or deep_search_designs is given a folderId. |
list_ordersread-only | List the seller's orders, newest first, 16 per page: order id, date, status, which shop or store it came from, the buyer's name, the total in USD and the items. Use it for the seller's latest orders or to find an order's id; get_order gives one order in full. |
list_productsread-only | List the seller's products, newest first, 24 per page: title, the blanks it is made on, when it was made, where it is (the store or shop it is in, or none when it is not in a store yet), price range, public link, status, how many items have been ordered, and the designId it is made from, which create_products can reuse at no credit cost. Leave storeId out to see every product, for questions like "did my last products go live" or "what is not in a store yet". |
list_product_typesread-only | Search the MyDesigns print-on-demand catalog: the blank products a design can be printed on (t-shirts, mugs, ...), with brand, product code, price range, number of variants and the print partners that make it. 24 per page. This is the catalog, not what the seller can make today: a product is made only from a profile, so use list_profiles for that. |
list_profilesread-only | List the product profiles a product can be made from. A profile is a saved set of products (t-shirt, mug, ...) with their print partner, colors, sizes, prices and mockups, so a design becomes a product without choosing each of those. Shows the seller's own profiles, or MyDesigns' public ones. Each has its products with colors, sizes and price range. These are the only products the seller can make: when neither their own nor the public profiles have one, it cannot be made. 24 per page. |
list_store_domainsread-only | List a store's own domains (like shop.example.com): whether each is live, which one is the main link buyers land on, and for each one not live yet the DNS record the seller must add where they bought the domain. A store has up to 3 domains. |
list_storesread-only | List the signed-in seller's MyDesigns stores with their public link, whether they can take orders yet (payouts connected), how many more stores the plan allows, and each store's about and contact details and seller info, with the seller info still missing. payoutAccounts are the seller's payout accounts, with the stores already on each, that a store can be put on with create_store or update_store. |
move_designs | Move designs into another of the seller's folders, by the ids list_designs gives, up to 100 at a time. Before moving more than a few, show the seller which go where and wait for their yes. Each folder is set up with its own image slots and fields, and designs move only between folders set up the same way; the result says which could not move and why. Those the seller moves in the MyDesigns app, where they choose where each image and field goes. |
product_creation_progressread-only | How far a product job has got. The product card calls this while it is open. |
publish_products | Put products into one of the seller's MyDesigns stores, where buyers can see and order them. Give either the jobId a create_products call returned, once get_product_status says READY (or FAILED, which publishes the ones that were made), or the productIds of products from list_products that are not in a store yet, e.g. ones made in an earlier chat. Products already in a store cannot be published again. Ask the seller which store when they have more than one; never pick one for them. The products then go into the store in the background over a few minutes: check with get_product_status and the jobIds returned here, and tell the seller when they are live. |
remove_store_domaindestructive | Disconnect a domain from its store; the seller keeps owning it. If it was the main link, the store's MyDesigns link takes over. Ask the seller before removing one. |
save_store_imagedestructive | Puts one file from the store image upload card on the store. The card calls this. |
save_uploaded_design | Saves one file from the upload card as a design. The card calls this. |
set_store_main_domain | Choose the store's main link: one of its domains, or with no domainId its own MyDesigns link. Its other links send buyers to the main one. Choose a domain only once it is live. |
update_seller_infodestructive | Change the seller info of one of the seller's stores: who sells there (a person or a business), their legal address and how to reach them. The store's legal pages show it, so fill it only with what the seller tells you: never guess or make up a name, address or VAT number. Only the values given change, but the store keeps seller info only when it is complete, as the app does: when list_stores shows some missing, ask the seller for all of it first, then make one call. |
update_storedestructive | Change a store's name, description, accent color, banner text, the logo's size and whether the store name shows next to it in the header, or its About page: the about text, the contact email, phone and address, and links to its social media. Only the values given change; everything else stays as it is; images are made with create_store_images or uploaded with upload_store_image, and the seller info is changed with update_seller_info. To remove a value or an image and go back to the store's default, name it in clear. payoutAccountId puts the store on one of the seller's payout accounts from list_stores: ask the seller first, naming the account by the stores already on it. |
upload_designs | Open a card where the seller uploads their own images (PNG or JPEG, up to 20 MB each) as designs. Use it when the seller wants products from art they already have: you cannot take an image from the chat, and never write a prompt to recreate one. The card saves the files and then gives you their designIds, which create_products takes. Uploading costs nothing. |
upload_store_imagedestructive | Open a card where the seller uploads their own images for one of their stores: the logo, the banner across the top of the home page, a separate banner for phones, or the favicon (the small icon in the browser tab). Use it when the seller already has the image: you cannot take an image from the chat. The card resizes each file and puts it on the store straight away, in place of the one there; it is not saved in the seller's designs. Free. Nothing comes back to you: when the seller says they are done, the images are on the store. |
Schemas: list_tools.
{
"name": "io.mydesigns/mcp",
"icons": [
{
"src": "https://mcp.mydesigns.io/icon-512.png",
"sizes": [
"512x512"
],
"mimeType": "image/png"
},
{
"src": "https://mcp.mydesigns.io/favicon.png",
"sizes": [
"96x96"
],
"mimeType": "image/png"
},
{
"src": "https://mcp.mydesigns.io/favicon.svg",
"sizes": [
"any"
],
"mimeType": "image/svg+xml"
}
],
"title": "MyDesigns",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://mcp.mydesigns.io/mcp",
"type": "streamable-http"
}
],
"version": "1.0.1",
"websiteUrl": "https://mydesigns.io/mcp",
"description": "Create print-on-demand products, publish them to your MyDesigns store, and track sales."
}