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/commands/implement.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/commands/southleft/figma-console-mcp/implement)<a href="https://agentmods.dev/commands/southleft/figma-console-mcp/implement"><img src="https://agentmods.dev/badge/commands/southleft/figma-console-mcp/implement/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/southleft/figma-console-mcp/implement"><img src="https://agentmods.dev/badge/commands/southleft/figma-console-mcp/implement.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00324 |
| Opus 5.5 | $0.00000 | $0.00130 |
| Sonnet 5.5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
implement 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 1mo 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.
What it actually says
Implement Command
Implement a feature or fix using best practices for this MCP server project.
Instructions
When implementing features for the Figma Console MCP server:
-
Use MCP SDK Patterns
- Follow Model Context Protocol TypeScript SDK conventions
- Use
McpServerfrom@modelcontextprotocol/sdk/server/mcp.js - Use Zod for input schema validation
- Return proper content structures:
{ content: [{ type: "text", text: "..." }] }
-
Follow Architecture
- Maintain separation of concerns (Server → Tools → Managers)
- Use Puppeteer for browser automation
- Use Chrome DevTools Protocol for console monitoring
- Implement intelligent log truncation (from AgentDesk patterns)
-
Code Quality
- Write TypeScript with strict mode
- Add JSDoc comments for public APIs
- Follow existing code style (Biome)
- Write tests for new features (Jest)
-
Code Style
- Use Biome for formatting and linting
- Run
npm run formatandnpm run lint:fix
-
Testing
- Unit tests for business logic
- Integration tests for tool handlers
- Maintain 70%+ code coverage
-
Documentation
- Update README.md if adding new tools
- Add inline comments for complex logic
Example Usage
/sc:implement Add error categorization to console logs
This will activate the implementation agent with context about the MCP server project.
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.
- 1mo ago First seen · 47 lines · 0 tokens per session scan A de82f673c976
implement is a command published in the GitHub repository southleft/figma-console-mcp (2,599 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 324 tokens. 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 commands, from other repositories
sheleg-design
Apply SHELEG Design to the current landing, hero, motion or product UI task.
slo-implement
You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based engineering practices. Design comprehensive SLO frameworks, establish meaningful SLIs, and create monitoring systems that balance reliability with feature velocity.
ui-synth
Master orchestration command that synthesizes ALL LibreUIUX plugins - archetypal-alchemy, design-mastery, accessibility, security, performance, testing - into one cohesive, production-ready UI/UX implementation. The ultimate synthesis.
setup
Kullanıcı "kur", "setup", "install", "bunu kur", GitHub linki verip kurulum isterse bu komutu uygula.
brand-update
Carry a positioning, pricing or naming change through the whole brand pack.
ux
Single entry point for all UX work, status across every layer, then the next action.