@adobe/design-data-agent-mcp 1.9.0 → 1.9.2

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 CHANGED
@@ -26,17 +26,26 @@ https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-agent-
26
26
  ### npm (MCP server)
27
27
 
28
28
  ```sh
29
- npx @adobe/design-data-agent-mcp
29
+ npx @adobe/design-data-agent-mcp@latest
30
30
  ```
31
31
 
32
32
  The `@adobe/design-data` CLI binary is **only** needed for `authoring_session_step_intent`. All other tools run in-process. Set `DESIGN_DATA_BIN` if the binary is not on `PATH`.
33
33
 
34
+ ### Staying current
35
+
36
+ The embedded Spectrum snapshot is baked into the wasm at build time and travels with the
37
+ package version — there's no separate data update to run. Pin `@latest` (as above) so `npx`
38
+ fetches the newest published version rather than reusing whatever it last cached; `-y` alone
39
+ only skips the install confirmation, it doesn't force a re-fetch. Already on `/plugin`? Run
40
+ `/plugin update design-data-agent@spectrum-design-data`. Call the primer tool and check
41
+ `provenance.designDataVersion` to see which dataset version is embedded.
42
+
34
43
  ## MCP server
35
44
 
36
45
  Configure your MCP client to run:
37
46
 
38
47
  ```sh
39
- npx -y @adobe/design-data-agent-mcp
48
+ npx -y @adobe/design-data-agent-mcp@latest
40
49
  ```
41
50
 
42
51
  Or from a repo clone:
@@ -100,7 +109,7 @@ node tools/design-data-agent-mcp/src/index.js
100
109
  "mcpServers": {
101
110
  "design-data-agent": {
102
111
  "command": "npx",
103
- "args": ["-y", "@adobe/design-data-agent-mcp"],
112
+ "args": ["-y", "@adobe/design-data-agent-mcp@latest"],
104
113
  "env": {
105
114
  "DESIGN_DATA_ROOT": "/abs/path/to/your/repo",
106
115
  "DESIGN_DATA_PATH": "packages/design-data/tokens",
@@ -119,7 +128,7 @@ node tools/design-data-agent-mcp/src/index.js
119
128
  "mcpServers": {
120
129
  "design-data-agent": {
121
130
  "command": "npx",
122
- "args": ["-y", "@adobe/design-data-agent-mcp"],
131
+ "args": ["-y", "@adobe/design-data-agent-mcp@latest"],
123
132
  "env": {
124
133
  "DESIGN_DATA_BIN": "design-data",
125
134
  "DESIGN_DATA_PATH": "/path/to/your/dataset"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@adobe/design-data-agent-mcp",
3
- "version": "1.9.0",
3
+ "version": "1.9.2",
4
4
  "description": "MCP server and Claude Code skill for the design-data agent surface — read tools run in-process via wasm",
5
5
  "type": "module",
6
6
  "main": "./src/index.js",
@@ -32,7 +32,7 @@
32
32
  "@modelcontextprotocol/sdk": "^1.27.1",
33
33
  "@adobe/design-data": "3.0.7",
34
34
  "@adobe/design-data-wasm": "0.7.0",
35
- "@adobe/spectrum-design-data": "2.3.0"
35
+ "@adobe/spectrum-design-data": "2.4.0"
36
36
  },
37
37
  "devDependencies": {
38
38
  "ava": "^6.0.1"
@@ -6,7 +6,7 @@ description: >
6
6
  system, token lookup, spec-conformance, drift detection, or token authoring on custom data.
7
7
  metadata:
8
8
  author: adobe
9
- version: "1.9.0"
9
+ version: "1.9.2"
10
10
  when_to_use: >
11
11
  Trigger on: design system, design tokens, spec-conformant, drift, validate tokens, token
12
12
  authoring, custom dataset, DESIGN_DATA_PATH, design-data validate, design-data diff,
@@ -38,7 +38,7 @@ Add `@adobe/design-data-agent-mcp` to your `.cursor/mcp.json`:
38
38
  "mcpServers": {
39
39
  "design-data-agent": {
40
40
  "command": "npx",
41
- "args": ["-y", "@adobe/design-data-agent-mcp"],
41
+ "args": ["-y", "@adobe/design-data-agent-mcp@latest"],
42
42
  "env": {
43
43
  "DESIGN_DATA_PATH": "./packages/tokens/src",
44
44
  "DESIGN_DATA_COMPONENTS": "./packages/design-data/components",
@@ -49,7 +49,9 @@ Add `@adobe/design-data-agent-mcp` to your `.cursor/mcp.json`:
49
49
  }
50
50
  ```
51
51
 
52
- Adjust paths to match your dataset layout.
52
+ Adjust paths to match your dataset layout. Pin `@latest` — the embedded Spectrum snapshot is
53
+ baked into the wasm at build time and travels with the package version, so there's no separate
54
+ data update to run, but plain `npx -y <pkg>` (no tag) can reuse a cached older build.
53
55
 
54
56
  ***
55
57
 
package/src/index.js CHANGED
@@ -48,7 +48,17 @@ export function createMCPServer() {
48
48
  const allTools = createAllTools();
49
49
  const server = new Server(
50
50
  { name: "design-data-agent-mcp", version: pkg.version },
51
- { capabilities: { tools: {} } },
51
+ {
52
+ capabilities: { tools: {} },
53
+ instructions:
54
+ "This server bundles a snapshot of Spectrum design data (tokens, components, " +
55
+ "guidelines) baked into its wasm at build time. The data version travels with the " +
56
+ "package version, so there is nothing to update separately. To get newer Spectrum " +
57
+ "data, install the latest published package (npx -y @adobe/design-data-agent-mcp@latest " +
58
+ '— plain "npx -y @adobe/design-data-agent-mcp" can reuse a cached older build). Call ' +
59
+ "the design-data primer tool and read provenance.designDataVersion to see the " +
60
+ "embedded dataset version.",
61
+ },
52
62
  );
53
63
  server.setRequestHandler(ListToolsRequestSchema, async () => ({
54
64
  tools: allTools.map(({ name, description, inputSchema }) => ({