Figma i18n MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_TOKEN | Yes | Your Figma access token used to authenticate with the Figma API. You can generate this in Figma under Settings -> Account -> Personal Access Tokens. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_figma_i18nA | Extracts all visible text from a Figma file, grouped by frame/component, for i18n translation. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly defined and distinct.
With a single tool, naming consistency is trivially maintained. The name 'extract_figma_i18n' clearly follows a verb_noun pattern.
The server has exactly one tool, which is borderline for a focused purpose. It is thin but not unreasonable for a niche i18n extraction utility.
The tool fully covers the stated purpose of extracting visible text for i18n. However, one might expect additional capabilities like filtering or writing translations back, but these are not necessarily core to the server's stated scope.