Lawrence's Personal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
|---|---|
| figma_get_fileA | Fetch a Figma file structure and metadata. Returns the full file tree including all pages, frames, and components. |
| figma_get_componentA | Get detailed information about a specific component in a Figma file, including its properties, variants, and styling. |
| figma_extract_design_tokensB | Extract design tokens (colors, typography, spacing, etc.) from a Figma file. Useful for generating CSS variables or theme files. |
| figma_search_componentsB | Search for components in a Figma file by name or type (e.g., "button", "input", "form"). |
| a11y_audit_componentB | Audit a React/HTML component for accessibility issues. Checks for WCAG compliance, ARIA attributes, semantic HTML, keyboard navigation, and color contrast. |
| a11y_suggest_improvementsC | Get specific accessibility improvement suggestions for a component, with code examples. |
| codegen_react_componentB | Generate a React component from Figma component data. Creates accessible, production-ready code with TypeScript support. |
| codegen_design_tokensA | Generate CSS variables or TypeScript design tokens from Figma design system. |
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 8 tools
Each tool targets a distinct step in a design-to-code workflow, and the Figma, a11y, and codegen prefixes help separate concerns. However, figma_extract_design_tokens vs codegen_design_tokens and a11y_audit_component vs a11y_suggest_improvements are close enough that an agent might occasionally pick the wrong one.
All tools follow a consistent snake_case verb_noun naming pattern within their respective domains, such as figma_get_file, a11y_audit_component, and codegen_react_component. The prefixes are predictable and group related functionality clearly.
Eight tools is a well-scoped count for a server covering Figma access, accessibility auditing, and code generation. Each tool serves a distinct purpose, and the set feels neither bloated nor thin.
The tool surface covers the full intended workflow: fetching and searching Figma data, extracting design tokens, auditing components, generating components, and producing design token output. There are no obvious dead ends or critical missing operations for the apparent design-to-code purpose.