figma-drive
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_TOKEN | Yes | Personal Access Token do Figma | |
| GOOGLE_CREDENTIALS_PATH | Yes | Caminho para o credentials.json do Service Account do Google |
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 |
|---|---|
| export_figma_framesB | Exporta frames do Figma como PNG em alta qualidade. Usa a API REST do Figma com batching automatico para evitar timeouts. |
| upload_to_driveA | Faz upload de arquivos para o Google Drive do cliente. Navega automaticamente a hierarquia: Clientes > [cliente] > Cronograma de Conteudo > Artes > [ano] > [mes] > [data]. Cria pastas inexistentes. |
| figma_to_driveC | Pipeline completo: exporta frames do Figma e faz upload para o Google Drive. Parse automatico do nome do frame no formato "[DATA] - [NOME]" para determinar cliente e data. |
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 3 tools
The three tools are mostly distinct: export_figma_frames only exports, upload_to_drive only uploads, and figma_to_drive combines both with parsing. There is slight overlap due to figma_to_drive covering the other two, but descriptions clarify the pipeline's additional functionality.
Two tools follow verb_noun snake_case (export_figma_frames, upload_to_drive), but figma_to_drive breaks pattern by using a description phrase. Consistent otherwise.
Three tools is on the lower side but appropriate for a focused figma-to-drive integration. Each tool serves a clear purpose, and the pipeline reduces redundancy.
Covers the core export-upload workflow, but lacks features like listing frames or managing Drive files. The pipeline assumes a specific naming convention, which may limit flexibility.