Figma Console MCP is a Model Context Protocol server that lets AI assistants access Figma as an interface for working with design systems. It supports extracting, creating, debugging, and synchronizing design tokens between Figma and codebases. The catalogue commands and instruction help agents use this workflow.
Borrowing it
Nothing to install: this file belongs to southleft/figma-console-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/southleft/figma-console-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/southleft/figma-console-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/southleft/figma-console-mcp/claude-md)<a href="https://agentmods.dev/instructions/southleft/figma-console-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/southleft/figma-console-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00415 | $0.00415 |
| Opus 5 | $0.00208 | $0.00208 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
figma-console-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- figma-console-mcp CLAUDE.md — 100% identical, 0 lines differ
- figma-console-mcp CLAUDE.md — 100% identical, 0 lines differ
What it actually says
Figma Console MCP
The most comprehensive MCP server for Figma — design tokens, components, variables, and programmatic design creation.
Build & Test
npm run build # Compiles local + cloudflare + apps
npm run build:local # Local mode only (use if Cloudflare types fail)
npm test # Jest test suite
npx tsc --noEmit # Type-check (pre-existing errors in src/apps/*/ui/mcp-app.ts are expected)
Release Process
Before any release, read .notes/RELEASING.md and follow all five phases. Run scripts/release.sh for automated version/count updates before manual content edits.
Known Issues
Cloudflare build type error: fixed — the threethis.env as Envcasts insrc/index.tsare nowas unknown as Env, sonpm run build:cloudflareexits 0 and the fullnpm run buildchain (whichprepublishOnlyruns) succeeds.npm publish: no longer needed now that the build passes. Publishing runs in CI via--ignore-scripts.github/workflows/publish.yml(Trusted Publishing / OIDC) onv*tag pushes — no token, no 2FA prompt. Renaming that workflow file breaks publishing until the npm Trusted Publisher config is updated to match.- Pre-existing tsc errors:
src/apps/*/ui/mcp-app.tsDOM type errors are expected (separate tsconfig files).
Architecture
- Entry points:
src/local.ts(local/NPX mode),src/index.ts(Cloudflare Workers) - Tool registration:
registerXxxTools(server, getFigmaAPI, ...)pattern insrc/tools/ - Desktop Bridge: WebSocket (
src/core/websocket-server.ts) - Schema compatibility: No
z.any()— Gemini requires strictly typed Zod schemas
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 30 lines · 415 tokens per session scan A f6624c24f1e0
figma-console-mcp CLAUDE.md is an instructions file published in the GitHub repository southleft/figma-console-mcp (2,282 stars, last pushed today), licensed MIT. It adds 415 tokens to every session, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.