ds-mcp-sync
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERBOSE | No | Enable verbose logging | false |
| DS_ROOT_PATH | No | Path to the design system root directory | ../design-system |
| FIGMA_FILE_ID | Yes | The Figma file ID from the URL | |
| FIGMA_ACCESS_TOKEN | Yes | Your Figma personal access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_figma_updatesB | Check for new or updated components in Figma design system |
| sync_tokensA | Sync design tokens from Figma to DS |
| generate_componentC | Generate a specific component from Figma |
| sync_allC | Perform full synchronization between Figma and DS |
| validate_setupC | Validate MCP server configuration and connections |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: checking updates, generating a component, syncing all, syncing tokens, and validating setup. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_figma_updates, generate_component).
5 tools is well-scoped for a Figma-DS sync server, covering key operations without being too few or excessive.
The tools cover the full sync workflow: checking updates, generating components, syncing tokens, performing full sync, and validating setup. No major gaps apparent.