@adobe/spectrum-design-data-mcp 0.0.0-layout-20260209174611

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/CHANGELOG.md ADDED
@@ -0,0 +1,188 @@
1
+ # [**@adobe/spectrum-design-data-mcp**](https://github.com/adobe/spectrum-design-data-mcp)
2
+
3
+ ## 0.0.0-layout-20260209174611
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies []:
8
+ - @adobe/spectrum-tokens@0.0.0-layout-20260209174611
9
+
10
+ ## 1.0.13
11
+
12
+ ### Patch Changes
13
+
14
+ - [#669](https://github.com/adobe/spectrum-design-data/pull/669) [`ae68c41`](https://github.com/adobe/spectrum-design-data/commit/ae68c412101b32b114d0d56893d1214f5225210a) Thanks [@GarthDB](https://github.com/GarthDB)! - feat(tooling): add renamed property support to token processing tools
15
+
16
+ Updated token processing tools to extract and display the new `renamed` property:
17
+ - **MCP Token Processor**: Extracts `renamed`, `deprecated`, and `deprecated_comment`
18
+ properties in token results
19
+ - **CSV Generator**: Added `renamed`, `deprecated`, and `deprecated_comment` columns
20
+ to CSV export
21
+ - **Diff Generator**: Updated documentation - tool automatically tracks `renamed`
22
+ property changes
23
+
24
+ These updates support the new `renamed` property added to the token schema for
25
+ tracking 1:1 token replacements.
26
+
27
+ - Updated dependencies [[`ae68c41`](https://github.com/adobe/spectrum-design-data/commit/ae68c412101b32b114d0d56893d1214f5225210a)]:
28
+ - @adobe/spectrum-tokens@14.1.0
29
+
30
+ ## 1.0.12
31
+
32
+ ### Patch Changes
33
+
34
+ - [#632](https://github.com/adobe/spectrum-design-data/pull/632) [`fa28b11`](https://github.com/adobe/spectrum-design-data/commit/fa28b117c6b84776f4ebe9bb281c29e14e0d64b6) Thanks [@GarthDB](https://github.com/GarthDB)! - BREAKING CHANGE: Repository renamed from spectrum-tokens to
35
+ spectrum-design-data
36
+
37
+ **Breaking Changes:**
38
+ - JSON Schema `$id` URIs changed (spectrum-tokens → spectrum-design-data)
39
+ - External tools referencing schemas by `$id` must update references
40
+
41
+ **Changes:**
42
+ - Updated all GitHub repository and Pages URLs
43
+ - Updated schema base URIs to maintain consistency
44
+
45
+ **Note:** NPM package names unchanged. GitHub redirects are in place.
46
+
47
+ - Updated dependencies [[`fa28b11`](https://github.com/adobe/spectrum-design-data/commit/fa28b117c6b84776f4ebe9bb281c29e14e0d64b6)]:
48
+ - @adobe/spectrum-tokens@14.0.0
49
+ - @adobe/spectrum-component-api-schemas@6.0.0
50
+
51
+ ## 1.0.11
52
+
53
+ ### Patch Changes
54
+
55
+ - Updated dependencies \[[`ee2ceb5`](https://github.com/adobe/spectrum-design-data/commit/ee2ceb541dea5eb9b5267c861e44bfd804fd33a7)]:
56
+ - @adobe/spectrum-component-api-schemas@[5.0.1](https://github.com/adobe/spectrum-component-api-schemas/releases/tag/@adobe/spectrum-component-api-schemas@5.0.1)
57
+
58
+ ## 1.0.10
59
+
60
+ ### Patch Changes
61
+
62
+ - Updated dependencies \[[`f64bee3`](https://github.com/adobe/spectrum-design-data/commit/f64bee3900c874775f2d3424516786a0d644d057)]:
63
+ - @adobe/spectrum-tokens@[13.16.0](https://github.com/adobe/spectrum-design-data/releases/tag/@adobe/spectrum-tokens@13.16.0)
64
+
65
+ ## 1.0.10
66
+
67
+ ### Patch Changes
68
+
69
+ - Updated dependencies \[[`f64bee3`](https://github.com/adobe/spectrum-design-data/commit/f64bee3900c874775f2d3424516786a0d644d057)]:
70
+ - @adobe/spectrum-tokens@[13.16.0](https://github.com/adobe/spectrum-design-data/releases/tag/@adobe/spectrum-tokens@13.16.0)
71
+
72
+ ## 1.0.9
73
+
74
+ ### Patch Changes
75
+
76
+ - Updated dependencies \[[`a772572`](https://github.com/adobe/spectrum-design-data/commit/a772572de88c54d279c20d7148f6ac91eb941d2a)]:
77
+ - @adobe/spectrum-component-api-schemas@[5.0.0](https://github.com/adobe/spectrum-component-api-schemas/releases/tag/@adobe/spectrum-component-api-schemas@5.0.0)
78
+
79
+ ## 1.0.8
80
+
81
+ ### Patch Changes
82
+
83
+ - Updated dependencies \[[`433efdd`](https://github.com/adobe/spectrum-design-data/commit/433efdd18f9b0842ae55acac3cd0fbc1e5e5db58)]:
84
+ - [**@adobe/spectrum-component-api-schemas**](https://github.com/adobe/spectrum-component-api-schemas)[**@4**](https://github.com/4).0.0
85
+
86
+ ## 1.0.7
87
+
88
+ ### Patch Changes
89
+
90
+ - Updated dependencies \[[`13d9202`](https://github.com/adobe/spectrum-design-data/commit/13d920273c02c78d3748522de6a7c7ee39b39814)]:
91
+ - [**@adobe/spectrum-component-api-schemas**](https://github.com/adobe/spectrum-component-api-schemas)[**@3**](https://github.com/3).0.0
92
+
93
+ ## 1.0.6
94
+
95
+ ### Patch Changes
96
+
97
+ - [#595](https://github.com/adobe/spectrum-design-data/pull/595) [`53bc11e`](https://github.com/adobe/spectrum-design-data/commit/53bc11e1bfcc3a839cfc5dfbd63f59cc5e87a1c3) Thanks [@GarthDB](https://github.com/GarthDB)! - Enhanced documentation with security and configuration improvements
98
+ - Add multiple MCP configuration options including recommended npx usage
99
+ - Add npm provenance support for enhanced supply-chain security
100
+ - Improve installation section with package integrity verification
101
+ - Add comprehensive troubleshooting section for common issues
102
+ - Add dedicated security section with best practices
103
+ - Add support section with links to issues and documentation
104
+
105
+ These changes align the documentation with modern MCP server standards
106
+ and improve user experience with better configuration options and security features.
107
+
108
+ ## 1.0.5
109
+
110
+ ### Patch Changes
111
+
112
+ - Updated dependencies \[[`1e860c4`](https://github.com/adobe/spectrum-design-data/commit/1e860c4436c58ceca6f4500ea7e24d6d8cdd20c8)]:
113
+ - @adobe/spectrum-tokens@[13.15.1](https://github.com/adobe/spectrum-design-data/releases/tag/@adobe/spectrum-tokens@13.15.1)
114
+
115
+ ## 1.0.4
116
+
117
+ ### Patch Changes
118
+
119
+ - Updated dependencies \[[`3df7197`](https://github.com/adobe/spectrum-design-data/commit/3df7197e7da23c9bb107f7dfcd935b5c62a86041)]:
120
+ - @adobe/spectrum-tokens@[13.15.0](https://github.com/adobe/spectrum-design-data/releases/tag/@adobe/spectrum-tokens@13.15.0)
121
+
122
+ ## 1.0.3
123
+
124
+ ### Patch Changes
125
+
126
+ - Updated dependencies \[[`b4df84e`](https://github.com/adobe/spectrum-design-data/commit/b4df84e2f2ca246332907f9ddda94438288dd98e)]:
127
+ - @adobe/spectrum-tokens@[13.14.1](https://github.com/adobe/spectrum-design-data/releases/tag/@adobe/spectrum-tokens@13.14.1)
128
+
129
+ ## 1.0.2
130
+
131
+ ### Patch Changes
132
+
133
+ - Updated dependencies \[[`336f672`](https://github.com/adobe/spectrum-design-data/commit/336f67216dfd875f0feb65c10059d9f3fe6dcaf7)]:
134
+ - @adobe/spectrum-tokens@[13.14.0](https://github.com/adobe/spectrum-design-data/releases/tag/@adobe/spectrum-tokens@13.14.0)
135
+
136
+ ## 1.0.1
137
+
138
+ ### Patch Changes
139
+
140
+ - Updated dependencies \[[`163fe7c`](https://github.com/adobe/spectrum-design-data/commit/163fe7c13bb00c639d202195a398126b6c25b58f)]:
141
+ - [**@adobe/spectrum-component-api-schemas**](https://github.com/adobe/spectrum-component-api-schemas)[**@2**](https://github.com/2).0.0
142
+
143
+ ## 1.0.0
144
+
145
+ ### Major Changes
146
+
147
+ - [#568](https://github.com/adobe/spectrum-design-data/pull/568) [`34028ea`](https://github.com/adobe/spectrum-design-data/commit/34028eaf2ba3940baa8044fda2655adc6153fb97) Thanks [@GarthDB](https://github.com/GarthDB)! - Initial release of Spectrum Design Data MCP server
148
+
149
+ This is the first release of the Model Context Protocol server that provides AI tools with structured access to Adobe Spectrum design system data, including design tokens and component API schemas.
150
+
151
+ Features:
152
+ - Query design tokens by name, type, or category
153
+ - Find tokens for specific component use cases
154
+ - Get component-specific token recommendations
155
+ - Access component API schemas and validation
156
+ - Type definitions and schema validation tools
157
+
158
+ This enables AI assistants to provide intelligent design guidance and automate design token usage across the Spectrum ecosystem.
159
+
160
+ ## 0.2.0
161
+
162
+ ### Minor Changes
163
+
164
+ - Initial release of Spectrum Design Data MCP server
165
+
166
+ This new package provides a Model Context Protocol (MCP) server that enables AI tools to query and interact with Spectrum design system data. Features include:
167
+ - **Design Token Tools**: Query tokens by name, type, or category; get token details and categories
168
+ - **Component Schema Tools**: Search component schemas, validate properties, and explore type definitions
169
+ - **Local Execution**: Runs as a local npm package with no external dependencies or hosting requirements
170
+ - **Extensible Architecture**: Designed to support future design data like component anatomy and patterns
171
+
172
+ The MCP server provides structured access to:
173
+ - All Spectrum design tokens from `@adobe/spectrum-tokens`
174
+ - Component API schemas from `@adobe/spectrum-component-api-schemas`
175
+
176
+ AI assistants can now understand and work with Spectrum design data through standardized MCP tools.
177
+
178
+ ## 0.1.0
179
+
180
+ ### Minor Changes
181
+
182
+ - Initial release of Spectrum Design Data MCP server
183
+ - Added support for design token querying and retrieval
184
+ - Added support for component schema validation and exploration
185
+ - Implemented token tools: query-tokens, get-token-categories, get-token-details
186
+ - Implemented schema tools: query-component-schemas, get-component-schema, list-components, validate-component-props, get-type-schemas
187
+ - Added CLI interface for starting the MCP server
188
+ - Added comprehensive test coverage
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "{}"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2017 Amazon.com, Inc. or its affiliates. All Rights Reserved.
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/README.md ADDED
@@ -0,0 +1,309 @@
1
+ # Spectrum Design Data MCP Server
2
+
3
+ A Model Context Protocol (MCP) server that provides AI tools with structured access to Adobe Spectrum design system data, including design tokens and component API schemas.
4
+
5
+ ## Overview
6
+
7
+ This MCP server enables AI assistants to query and interact with Spectrum design data through a standardized protocol. It provides access to:
8
+
9
+ * **Design Tokens**: Color palettes, typography, layout tokens, and semantic tokens
10
+ * **Component Schemas**: API definitions and validation schemas for Spectrum components
11
+ * **Future**: Component anatomy, design patterns, and guidelines
12
+
13
+ ## Prerequisites
14
+
15
+ * **Node.js 20+**
16
+
17
+ ## Installation
18
+
19
+ ```bash
20
+ npm install -g @adobe/spectrum-design-data-mcp
21
+ ```
22
+
23
+ ### Verifying Package Integrity
24
+
25
+ This package is published with npm provenance for enhanced supply-chain security. You can verify the package's attestations:
26
+
27
+ ```bash
28
+ npm audit signatures
29
+ ```
30
+
31
+ Or clone and run locally:
32
+
33
+ ```bash
34
+ git clone https://github.com/adobe/spectrum-design-data.git
35
+ cd spectrum-tokens/tools/spectrum-design-data-mcp
36
+ pnpm install
37
+ ```
38
+
39
+ ## Usage
40
+
41
+ ### Starting the MCP Server
42
+
43
+ ```bash
44
+ # Start the server (default command)
45
+ spectrum-design-data-mcp
46
+
47
+ # Or explicitly start
48
+ spectrum-design-data-mcp start
49
+ ```
50
+
51
+ The server runs locally and communicates via stdio with MCP-compatible AI clients.
52
+
53
+ ### Available Tools
54
+
55
+ #### Token Tools
56
+
57
+ * **`query-tokens`**: Search and retrieve design tokens by name, type, or category
58
+ * **`find-tokens-by-use-case`** ⭐: Find appropriate tokens for specific component use cases (e.g., "button background", "text color", "error state")
59
+ * **`get-component-tokens`** ⭐: Get all tokens related to a specific component type
60
+ * **`get-design-recommendations`** ⭐: Get token recommendations for design decisions and component states
61
+ * **`get-token-categories`**: List all available token categories
62
+ * **`get-token-details`**: Get detailed information about a specific token
63
+
64
+ #### Schema Tools
65
+
66
+ * **`query-component-schemas`**: Search component API schemas
67
+ * **`get-component-schema`**: Get the complete schema for a specific component
68
+ * **`list-components`**: List all available components with schemas
69
+ * **`validate-component-props`**: Validate component properties against schemas
70
+ * **`get-type-schemas`**: Get type definitions used in schemas
71
+
72
+ ## Configuration
73
+
74
+ ### MCP Setup
75
+
76
+ Add to your MCP configuration (e.g., `.cursor/mcp.json` for Cursor IDE):
77
+
78
+ #### Option 1: Using npx (Recommended)
79
+
80
+ ```json
81
+ {
82
+ "mcpServers": {
83
+ "spectrum-design-data": {
84
+ "command": "npx",
85
+ "args": ["@adobe/spectrum-design-data-mcp"]
86
+ }
87
+ }
88
+ }
89
+ ```
90
+
91
+ #### Option 2: Using global installation
92
+
93
+ ```json
94
+ {
95
+ "mcpServers": {
96
+ "spectrum-design-data": {
97
+ "command": "@adobe/spectrum-design-data-mcp"
98
+ }
99
+ }
100
+ }
101
+ ```
102
+
103
+ #### Option 3: Local development
104
+
105
+ ```json
106
+ {
107
+ "mcpServers": {
108
+ "spectrum-design-data": {
109
+ "command": "node",
110
+ "args": [
111
+ "./path/to/spectrum-tokens/tools/spectrum-design-data-mcp/src/index.js"
112
+ ]
113
+ }
114
+ }
115
+ }
116
+ ```
117
+
118
+ > **Note**: Using `npx` (Option 1) is recommended as it avoids PATH issues and ensures you always use the latest version. This approach mirrors other MCP servers like Browser MCP and resolves common NPX availability problems.
119
+
120
+ ### Claude Desktop (Legacy Configuration)
121
+
122
+ For older Claude Desktop configurations:
123
+
124
+ ```json
125
+ {
126
+ "mcpServers": {
127
+ "spectrum-design-data": {
128
+ "command": "spectrum-design-data-mcp",
129
+ "args": []
130
+ }
131
+ }
132
+ }
133
+ ```
134
+
135
+ ### Other MCP Clients
136
+
137
+ The server uses stdio transport and follows the MCP specification. Refer to your client's documentation for configuration details.
138
+
139
+ ## Examples
140
+
141
+ ### Component Building Workflow ⭐
142
+
143
+ #### Finding Tokens for Component Use Cases
144
+
145
+ ```
146
+ Human: I'm building a primary action button. What design tokens should I use for the background color?
147
+
148
+ AI: I'll help you find the appropriate tokens for a primary button background.
149
+
150
+ [Uses find-tokens-by-use-case with useCase="button background" and componentType="button"]
151
+
152
+ For a primary action button background, I recommend these Spectrum tokens:
153
+ - accent-color-100: Primary accent color for default state
154
+ - accent-color-200: For hover states
155
+ - accent-color-300: For pressed/active states
156
+ - floating-action-button-drop-shadow-color: For drop shadows
157
+ ```
158
+
159
+ #### Design Intent Recommendations
160
+
161
+ ```
162
+ Human: What tokens should I use for error messaging in my form validation?
163
+
164
+ AI: I'll find tokens for error state messaging.
165
+
166
+ [Uses get-design-recommendations with intent="negative" and context="text"]
167
+
168
+ For error messaging, use these Spectrum tokens:
169
+ - negative-color-100: Primary error text color
170
+ - negative-background-color-default: Error background areas
171
+ - negative-border-color: Error state borders
172
+ ```
173
+
174
+ #### Component-Specific Token Discovery
175
+
176
+ ```
177
+ Human: Show me all available button-related design tokens.
178
+
179
+ AI: I'll gather all button-related tokens from the Spectrum system.
180
+
181
+ [Uses get-component-tokens with componentName="button"]
182
+
183
+ Found 57 button-related tokens across categories:
184
+ - Color tokens (2): floating-action-button colors
185
+ - Layout tokens (55): button sizing, padding, spacing
186
+ - Examples: radio-button-control-size-small, action-button-edge-to-hold-icon...
187
+ ```
188
+
189
+ ### Traditional Token Queries
190
+
191
+ #### Querying Color Tokens
192
+
193
+ ```
194
+ Human: What blue color tokens are available in Spectrum?
195
+
196
+ AI: I'll search for blue color tokens in the Spectrum design system.
197
+
198
+ [Uses query-tokens tool with query="blue" and category="color"]
199
+
200
+ The Spectrum design system includes several blue color tokens:
201
+ - spectrum-blue-100: #e6f3ff
202
+ - spectrum-blue-200: #b3d9ff
203
+ - spectrum-blue-300: #80bfff
204
+ ...
205
+ ```
206
+
207
+ #### Validating Component Props
208
+
209
+ ```
210
+ Human: Is this button configuration valid according to Spectrum?
211
+
212
+ AI: I'll validate those button properties against the Spectrum schema.
213
+
214
+ [Uses validate-component-props tool with component="action-button"]
215
+
216
+ The configuration is valid! All required properties are present and the types match the expected schema.
217
+ ```
218
+
219
+ ## Troubleshooting
220
+
221
+ ### Installation Issues
222
+
223
+ ```bash
224
+ # Check Node.js version
225
+ node --version # Should be 20+
226
+
227
+ # Clear npm cache if needed
228
+ npm cache clean --force
229
+
230
+ # Verify package installation
231
+ npm list -g @adobe/spectrum-design-data-mcp
232
+ ```
233
+
234
+ ### MCP Connection Issues
235
+
236
+ 1. Verify the MCP configuration file path
237
+ 2. Check that Node.js path is correct
238
+ 3. Ensure the package is installed globally or use npx
239
+ 4. Restart your AI client after configuration changes
240
+
241
+ ### Package Verification
242
+
243
+ ```bash
244
+ # Verify package integrity
245
+ npm audit signatures
246
+
247
+ # Check for security vulnerabilities
248
+ npm audit
249
+ ```
250
+
251
+ ## Development
252
+
253
+ ### Building from Source
254
+
255
+ ```bash
256
+ git clone https://github.com/adobe/spectrum-design-data.git
257
+ cd spectrum-tokens
258
+ pnpm install
259
+ cd tools/spectrum-design-data-mcp
260
+ ```
261
+
262
+ ### Testing
263
+
264
+ ```bash
265
+ pnpm test
266
+ ```
267
+
268
+ ### Project Structure
269
+
270
+ ```
271
+ src/
272
+ ├── index.js # Main MCP server
273
+ ├── cli.js # CLI interface
274
+ ├── tools/ # MCP tool implementations
275
+ │ ├── tokens.js # Token-related tools
276
+ │ └── schemas.js # Schema-related tools
277
+ └── data/ # Data access layer
278
+ ├── tokens.js # Token data access
279
+ └── schemas.js # Schema data access
280
+ ```
281
+
282
+ ## Security
283
+
284
+ ### Supply Chain Security
285
+
286
+ * **🔐 NPM Provenance**: Published with npm provenance attestations for verifiable builds
287
+ * **🛡️ Security Audits**: Regular dependency security audits
288
+ * **📦 Verified Packages**: All dependencies are audited and verified
289
+
290
+ ### Best Practices
291
+
292
+ * Always verify package integrity using `npm audit signatures`
293
+ * Keep the package updated to the latest version
294
+ * Use npx for the most secure and up-to-date execution
295
+ * Report security issues through the [GitHub security advisory](https://github.com/adobe/spectrum-design-data/security/advisories)
296
+
297
+ ## License
298
+
299
+ Apache-2.0 © Adobe
300
+
301
+ ## Contributing
302
+
303
+ This project is part of the Spectrum Design System. Please see the main [contribution guidelines](../../CONTRIBUTING.md) for details on how to contribute.
304
+
305
+ ## Support
306
+
307
+ * Create an [issue](https://github.com/adobe/spectrum-design-data/issues) for bug reports or feature requests
308
+ * Check the [documentation](https://github.com/adobe/spectrum-design-data/tree/main/tools/spectrum-design-data-mcp) for detailed guides
309
+ * Review [existing issues](https://github.com/adobe/spectrum-design-data/issues?q=label%3Amcp) for solutions