@productmaker/mcp 2.10.0 → 3.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/README.md +37 -15
  2. package/dist/http.js +203 -196
  3. package/dist/stdio.js +203 -196
  4. package/dist/ui/meta-upload-app.html +17 -74
  5. package/package.json +3 -3
package/README.md CHANGED
@@ -63,6 +63,36 @@ Sign up at [productmaker.app](https://productmaker.app) and create a key (prefix
63
63
 
64
64
  ## What you can do from your AI assistant
65
65
 
66
+ ### Guided dropshipping launch
67
+
68
+ The MCP exposes one guided prompt, `start_dropshipping`, for users who want
69
+ ProductMaker to lead the complete journey. It routes intent before acting: a
70
+ focused request to create a creative, publish to Shopify, or publish to Meta
71
+ continues through the corresponding tool without creating a project. The guided
72
+ flow uses the project's persisted phase and `guide_dropshipping_launch`'s
73
+ `nextAction` instead of maintaining a second checklist in the chat.
74
+
75
+ The launch flow asks for explicit confirmation before the 2,000-credit product
76
+ research run and before other paid or external mutations, uses the real supplier
77
+ cost for costing, pauses at user-review gates, and leaves Meta campaigns PAUSED.
78
+ It does not promise persistent memory, automatic next-day monitoring, traffic-light
79
+ decisions, campaign activation, budget changes, or automatic shutdown. For deeper
80
+ Meta metrics, the assistant may optionally suggest Meta's official MCP; that is
81
+ not required to use ProductMaker and is never claimed to be installed by this
82
+ server.
83
+
84
+ Use it in one of three ways: load the source-controlled Agent Plugin on a
85
+ compatible host and invoke `$start-dropshipping`, select the MCP prompt
86
+ `start_dropshipping` where prompts are supported, or ask any tool-only client in
87
+ natural language to guide an end-to-end launch. A focused creative, landing,
88
+ Shopify, Meta, or status request continues through its direct tool.
89
+
90
+ The plugin manifests intentionally contain no ProductMaker API key. The host
91
+ must provide the authenticated MCP connection through its secure connection or
92
+ credential flow; loading the skill alone does not prove that the remote endpoint
93
+ is authorized. Public OpenAI/“With MCP” registration and OAuth readiness are a
94
+ separate release step.
95
+
66
96
  | Tool | What it does |
67
97
  | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
68
98
  | `cost_product` | Estimate a safe Colombia/COP selling price for free, then reuse its `price` and `compareAtPrice` in `create_product_task` |
@@ -88,8 +118,6 @@ Sign up at [productmaker.app](https://productmaker.app) and create a key (prefix
88
118
  | `list_meta_destinations` | List Meta Business portfolios, ad accounts per portfolio, and Facebook Pages; use the returned IDs to choose the exact publication destination |
89
119
  | `request_media_upload` | Open the consumer-neutral inline file picker for ProductMaker tasks, image/video creatives, landings, and Meta; supports image, video, or mixed sessions, ChatGPT file references, an explicit OK chat handoff, and `/upload-media` only as fallback |
90
120
  | `check_media_upload` | Return verified owner-scoped opaque asset IDs and media kinds from a universal upload session; no bytes, token, file name, or private URL reaches the model |
91
- | `request_meta_media_upload` | Backward-compatible Meta upload alias; existing clients keep the legacy staged-source flow |
92
- | `check_meta_media_upload` | Backward-compatible Meta status alias returning legacy staged asset IDs |
93
121
  | `list_tiktok_advertisers` | List connected TikTok Ads advertiser accounts |
94
122
  | `publish_to_shopify` | Publish a completed task to a Shopify store (returns markdown with landing + product URLs) |
95
123
  | `publish_to_meta` | Create a Meta Ads campaign from a task (always PAUSED) after selecting exact `portfolioId`, `adAccountId`, and `pageId` with `list_meta_destinations` |
@@ -125,19 +153,13 @@ presses OK, continue the previous request with only the verified `assetId` and
125
153
  matching `mediaKind` values. `check_media_upload` remains available for hosts
126
154
  that need an explicit status call.
127
155
 
128
- Existing Meta clients may continue using `request_meta_media_upload` and
129
- `check_meta_media_upload`. For every legacy entry in `assets[]`, use its
130
- `mediaKind` as the creative `type` and its `stagingAssetId` as:
131
-
132
- ```json
133
- { "type": "staged", "stagingAssetId": "..." }
134
- ```
135
-
136
- inside `publish_creatives_to_meta`. A partial batch may include only the assets
137
- that `assets[]` actually reports as uploaded. The browser uploads directly to
138
- the presigned CDN object; the chat never receives file bytes, base64, or a
139
- local path, and ProductMaker deletes the staging object after a successful
140
- paused Meta publication (or via the 24-hour TTL cleanup if the flow is
156
+ For Meta, pass each verified asset as
157
+ `{ "type": "asset", "assetId": "..." }` to `publish_creatives_to_meta` after
158
+ the user chooses the portfolio, ad account, and page in chat. A partial batch
159
+ may include only the assets actually reported as uploaded. The browser uploads
160
+ directly to the presigned CDN object; the chat never receives file bytes,
161
+ base64, or a local path, and ProductMaker deletes the staging object after a
162
+ successful paused Meta publication (or via the 24-hour TTL cleanup if the flow is
141
163
  abandoned).
142
164
 
143
165
  ## Video duration and winner review