@dropins/mcp 0.2.0 → 0.3.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 +0 -35
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -239,41 +239,6 @@ In partial mode, only the targeted drop-in repos are branch/version checked, and
|
|
|
239
239
|
|
|
240
240
|
Block patterns and SDK package metadata (event-bus, fetch-graphql, etc.) are manually curated in `registry/sdk.json`. Elsie component props, slots, and exported types are auto-generated from StorefrontSDK source. Everything else is auto-generated by `yarn generate`.
|
|
241
241
|
|
|
242
|
-
### Usage analytics
|
|
243
|
-
|
|
244
|
-
The MCP server automatically logs every tool call to `.telemetry/usage.jsonl` (inside the MCP repo, gitignored) with timing, parameters, and result metadata.
|
|
245
|
-
|
|
246
|
-
Run `yarn stats` to view usage patterns:
|
|
247
|
-
|
|
248
|
-
- Tool call frequency and empty result rates (identifies knowledge gaps)
|
|
249
|
-
- Most queried drop-ins (shows developer interest)
|
|
250
|
-
- Failed search queries (actionable improvement list)
|
|
251
|
-
- Response times and error rates per tool
|
|
252
|
-
|
|
253
|
-
Example output:
|
|
254
|
-
|
|
255
|
-
```text
|
|
256
|
-
=== Dropins MCP Usage Stats ===
|
|
257
|
-
Period: last 30 days (247 total calls, 12% empty)
|
|
258
|
-
|
|
259
|
-
Top tools
|
|
260
|
-
Tool Calls Empty% Errors Avg ms
|
|
261
|
-
──────────────────────────────────────────────────────────
|
|
262
|
-
list_slots 61 2% 0 11
|
|
263
|
-
search_docs 39 21% 0 34 ← knowledge gap
|
|
264
|
-
list_graphql_queries 48 4% 0 18
|
|
265
|
-
|
|
266
|
-
Top empty-result queries (fix these)
|
|
267
|
-
8x "reCAPTCHA setup"
|
|
268
|
-
5x "B2B quote workflow"
|
|
269
|
-
```
|
|
270
|
-
|
|
271
|
-
Entries older than 90 days are automatically cleaned up on each run. Use `yarn stats --days 30` to narrow the window. The log file persists across MCP restarts and different projects.
|
|
272
|
-
|
|
273
|
-
For a visual dashboard with interactive charts, run `yarn dashboard`. This opens a React Spectrum app showing usage over time, tool breakdown, empty result queries, and dropin interest trends.
|
|
274
|
-
|
|
275
|
-
**Sharing feedback:** Consider sharing your `yarn stats` output with the MCP development team to help prioritize improvements and identify common knowledge gaps.
|
|
276
|
-
|
|
277
242
|
### When to regenerate
|
|
278
243
|
|
|
279
244
|
The knowledge base should be regenerated after every official drop-in release that includes stable versions. This ensures the MCP reflects the latest containers, slots, events, API functions, and documentation available to merchants. Make sure all local drop-in clones are on their default branch and up to date before running `yarn generate`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@dropins/mcp",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"description": "MCP server for Adobe Commerce Storefront Dropins — provides AI assistants with deep knowledge of blocks, slots, extensions, events, and design tokens",
|
|
5
5
|
"license": "SEE LICENSE IN LICENSE.md",
|
|
6
6
|
"author": "Adobe Commerce Storefront Team",
|