Ds Mcp Sync — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Ds Mcp Sync (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An MCP (Model Context Protocol) server that enables seamless synchronization between your Figma design system and your Design System codebase.
git clone <repository-url>
cd ds-mcp-sync
npm install
npm run buildCreate a config/mcp-config.json file or set environment variables:
{
"figma": {
"fileId": "your-figma-file-id",
"accessToken": "your-figma-personal-access-token",
"componentPrefix": "DS"
},
"mds": {
"rootPath": "../design-system",
"componentPath": "component-lib/components",
"tokenPath": "component-lib/tokens",
"storybookPath": "component-lib/.storybook"
}
}Environment Variables (alternative):
export FIGMA_ACCESS_TOKEN="your-token-here"
export FIGMA_FILE_ID="your-file-id"
export DS_ROOT_PATH="../design-system"From your Figma design system URL:
https://www.figma.com/file/ABC123DEF456/Design-System
^^^^^^^^^^^^
This is your file IDAdd this server to your Claude Code MCP configuration:
macOS/Linux: ~/.claude_mcp.json Windows: %APPDATA%\Claude\claude_mcp.json
{
"mcpServers": {
"ds-mcp-sync": {
"command": "node",
"args": ["/path/to/ds-mcp-sync/dist/index.js"],
"env": {
"FIGMA_ACCESS_TOKEN": "your-token",
"FIGMA_FILE_ID": "your-file-id"
}
}
}
}Once configured, you can use these commands in Claude Code:
claude "Check if there are any new components in Figma"claude "Sync design tokens from Figma to DS"claude "Generate the Button component from Figma"claude "Sync all new components from Figma to DS"claude "Validate the MCP server setup"| Tool | Description |
|---|---|
check_figma_updates | Compare Figma with current DS and report differences |
sync_tokens | Extract and update design tokens from Figma styles |
generate_component | Create a specific component with TypeScript and stories |
sync_all | Perform complete synchronization (with optional dry-run) |
validate_setup | Test Figma connection and validate configuration |
colors.primary.500)component-lib/tokens/tokens.tscomponent-lib/
├── components/
│ ├── atoms/
│ │ └── Button/
│ │ ├── Button.tsx
│ │ ├── Button.stories.tsx
│ │ └── index.ts
│ ├── molecules/
│ └── organisms/
└── tokens/
└── tokens.ts| Figma Component | Atomic Level | Reason |
|---|---|---|
| Button, Input, Icon | Atoms | Basic UI elements |
| Card, Modal, Dropdown | Molecules | Groups of atoms |
| Header, Table, Navigation | Organisms | Complex layouts |
{
"figma": {
"fileId": "string", // Required: Figma file ID
"accessToken": "string", // Required: Personal access token
"componentPrefix": "string" // Optional: Filter components by prefix
},
"mds": {
"rootPath": "string", // Path to MDS root directory
"componentPath": "string", // Relative path to components
"tokenPath": "string", // Relative path to tokens
"storybookPath": "string" // Relative path to Storybook config
},
"dryRun": false, // Run without making file changes
"verbose": true // Enable detailed logging
}"Figma API connection failed"
"DS paths not accessible"
rootPath points to your DS directory"Component generation failed"
Set verbose: true in config or VERBOSE=true environment variable for detailed logging.
# Development mode with hot reload
npm run dev
# Build for production
npm run build
# Run linting
npm run lint
# Type checking
npm run typecheckMIT License - see LICENSE file for details.
Need help? Check the troubleshooting section or create an issue on GitHub.# ds-mcp-sync
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.