mcp-server-sfmc 0.1.8 → 0.2.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.
- package/README.md +70 -0
- package/bundled/mce-help/chunks.json +1 -1
- package/dist/index.js +96 -38
- package/dist/index.js.map +1 -1
- package/dist/mce-help-search.d.ts +3 -2
- package/dist/mce-help-search.d.ts.map +1 -1
- package/dist/mce-help-search.js +17 -7
- package/dist/mce-help-search.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -166,6 +166,76 @@ Access via `/mcp.sfmc.writeAmpscript` etc. in VS Code, or via the prompts API:
|
|
|
166
166
|
| `convertAmpscriptToSsjs` | Convert AMPscript code to equivalent SSJS |
|
|
167
167
|
| `answerMceHowTo` | Guided prompt for admin/setup questions — searches bundled help and keeps Engagement vs Next explicit |
|
|
168
168
|
|
|
169
|
+
## Writing effective prompts
|
|
170
|
+
|
|
171
|
+
### Automatic tool use
|
|
172
|
+
|
|
173
|
+
Clients that honour the MCP `instructions` field (Cursor, Claude Desktop, GitHub Copilot Agent mode) will call `search_mce_help` automatically whenever you ask an MCE administration or setup question — no special phrasing needed. If your client does not process server instructions, or if you want explicit control, the templates below help.
|
|
174
|
+
|
|
175
|
+
### Quick reference: which tool or prompt to use
|
|
176
|
+
|
|
177
|
+
| Situation | What to do |
|
|
178
|
+
|---|---|
|
|
179
|
+
| MCE admin question (classic Engagement) | Ask naturally; the server will call `search_mce_help` for you. Or use the `answerMceHowTo` prompt with `assumeProduct: engagement`. |
|
|
180
|
+
| Marketing Cloud Next question | Use `answerMceHowTo` with `assumeProduct: next`, or add "for Marketing Cloud Next" to your question. |
|
|
181
|
+
| Not sure which product | Use `answerMceHowTo` with `assumeProduct: unsure`, or add "check both Engagement and Next" to your question. |
|
|
182
|
+
| Write or validate AMPscript | Use the `writeAmpscript` prompt, or ask directly (the server auto-validates). |
|
|
183
|
+
| Write or validate SSJS | Use the `writeSsjs` prompt, or ask directly. |
|
|
184
|
+
| Review a code diff | Use the `reviewSfmcCode` prompt or mention "review the following diff". |
|
|
185
|
+
|
|
186
|
+
### Copy-paste prompt templates
|
|
187
|
+
|
|
188
|
+
#### Classic Engagement admin (most common)
|
|
189
|
+
|
|
190
|
+
```
|
|
191
|
+
Search the Marketing Cloud Engagement help (product_focus: engagement) and tell me:
|
|
192
|
+
<your question here>
|
|
193
|
+
|
|
194
|
+
Cite which product version your steps apply to and note if the bundled docs are incomplete.
|
|
195
|
+
```
|
|
196
|
+
|
|
197
|
+
#### Marketing Cloud Next
|
|
198
|
+
|
|
199
|
+
```
|
|
200
|
+
Search the Marketing Cloud Next help (product_focus: next) and tell me:
|
|
201
|
+
<your question here>
|
|
202
|
+
|
|
203
|
+
Confirm the steps apply to Marketing Cloud Next, not classic Engagement.
|
|
204
|
+
```
|
|
205
|
+
|
|
206
|
+
#### Unknown product / migration question
|
|
207
|
+
|
|
208
|
+
```
|
|
209
|
+
Search both Marketing Cloud Engagement and Next help (product_focus: any) and tell me:
|
|
210
|
+
<your question here>
|
|
211
|
+
|
|
212
|
+
Separate the steps for classic Engagement vs Marketing Cloud Next clearly.
|
|
213
|
+
```
|
|
214
|
+
|
|
215
|
+
#### Explicit use of the answerMceHowTo prompt
|
|
216
|
+
|
|
217
|
+
In clients that support MCP prompts (e.g. VS Code with the `/mcp.sfmc.answerMceHowTo` command):
|
|
218
|
+
|
|
219
|
+
```
|
|
220
|
+
/mcp.sfmc.answerMceHowTo
|
|
221
|
+
question: "How do I create a child business unit and assign it a sender profile?"
|
|
222
|
+
assumeProduct: engagement
|
|
223
|
+
```
|
|
224
|
+
|
|
225
|
+
#### Combining MCE admin with code
|
|
226
|
+
|
|
227
|
+
```
|
|
228
|
+
1. Use search_mce_help (product_focus: engagement) to find the correct Journey Builder entry event
|
|
229
|
+
configuration steps, then
|
|
230
|
+
2. Write the AMPscript snippet that reads the data extension row inside the journey email.
|
|
231
|
+
```
|
|
232
|
+
|
|
233
|
+
### What to expect from the AI
|
|
234
|
+
|
|
235
|
+
- The AI cites the product scope (Engagement or Next) in every answer.
|
|
236
|
+
- If the bundled excerpts do not cover the question fully, the AI says so and suggests verifying in the live Salesforce Help.
|
|
237
|
+
- Function signatures (AMPscript / SSJS) are always sourced from the language catalog, not from training data.
|
|
238
|
+
|
|
169
239
|
## Refresh bundled Marketing Cloud Engagement help
|
|
170
240
|
|
|
171
241
|
The published npm package includes `bundled/mce-help/chunks.json`, built from a checkout that contains the mirrored Help tree at `docs/help.salesforce/mce` (for example in this monorepo). To regenerate after updating those docs:
|