Automating Figma Workflows with Vox and MCP
Figma now has an official MCP server. Connect it to Vox once and you can talk to your design files in plain English — no more manually copying color tokens, hunting for component names, or exporting assets one by one.
Setup: connect Figma MCP
Open the Vox Tools panel → MCP Servers → Connect. Set the transport to stdio and use this command:
npx -y figma-developer-mcp --figma-api-key=YOUR_TOKEN
Get your token from figma.com/settings → Personal access tokens. Paste the token as a secret instead of inline if you prefer.
Hit Sync. Vox imports all available Figma tools into its library.
What you can do
“Computer, list all the components in my design system file.”
“Computer, extract all color tokens from my Figma file and format them as CSS variables.”
“Computer, what changed in my Figma file since last week?”
Why this is better than the Figma plugin
The Figma Dev Mode plugin is great for inspecting a single component. But Vox operates across your entire file — and can chain Figma actions with other tools. Extract your tokens, format them as CSS, and write them directly to your codebase in one command.
Vox can combine Figma MCP with its built-in file tools. "Extract my design tokens and commit them to my repo" would use Figma MCP to read the tokens and run_local_command to run git commit.
Put Vox to work on your computer.
Download Vox for Mac and start with the local setup flow.
macOS · Apple Silicon & Intel