figmanage
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| setup_statusA | Check figmanage authentication status and get setup instructions. Always call this before using any other tool. |
| setup_extract_cookiesA | Extract Figma session cookies from Chrome. On macOS this triggers a Keychain prompt. IMPORTANT: Before calling, confirm the user is logged into figma.com in Chrome and knows a system prompt may appear. |
| setup_select_accountA | Select a Figma account and validate the session. Call after setup_extract_cookies. |
| setup_save_patA | Validate and save a Figma Personal Access Token. Completes setup and activates all tools. |
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 4 tools
Each tool covers a distinct setup step or authentication method: status, cookie extraction, account selection, and PAT storage. The descriptions and stated sequencing make it unlikely an agent would confuse them.
All tools share the setup_ prefix and mostly follow a setup_verb_noun pattern. setup_status is the one minor deviation, since status is a noun rather than a verb.
Four tools is a reasonable count for an onboarding and authentication workflow. It is slightly on the low side for a server named figmanage, but each tool fills a necessary setup role.
The setup flow itself is covered end to end, but the server exposes no actual Figma management, file, or project tools. After setup is complete, there is no way for an agent to perform real work, which is a significant gap for a server called figmanage.