figma
v0.0.2by HiAi-gg · author: HiAI
Bring Figma design context into agent workflows: inspect design context, implement from design, map components, and compare code to design, via Figma's official MCP server.
What figma does, in the publisher's words
Bring Figma design context into agent workflows: inspect design context, implement from design, map components, and compare code to design, via Figma's official MCP server.
An Agent Plugin (spec 1.0.0).
A plugin that connects agents to Figma's official remote MCP server (https://mcp.figma.com/mcp) and adds four portable workflow skills for design-informed implementation and verification.
- First-party upstream: Figma's own remote MCP server.
- Workflow value: the skills teach how to use design context (tokens, components, screenshots) to implement and verify, not just what the tools do.
- Portable: the skills are original, portable workflows; Figma's client-specific plugin skills (Claude Code/Cursor) remain the recommended option inside those clients.
- Server: figma: streamable-http to https://mcp.figma.com/mcp (Figma-hosted, vendor-operated; endpoint version not pinnable).
- Skills: inspect-design-context, implement-from-design, map-design-components, compare-code-to-design.
- An MCP client that supports streamable-http and OAuth, and is in the Figma MCP Catalog.
From the project README, punctuation lightly normalized · Open the README on GitHub
- Skills
- 4
- MCP servers
- 1
- Stars
- 1
- License
- MIT
- Repo created
- 2026-08-08
- Last pushed
- 2026-09-03
- Publisher type
- Organization
- Version
- 0.0.2
Links
Skills · 4
- compare-code-to-design
- Compare implemented UI code against its Figma design: fetch the design context and screenshot, inspect the implementation, and report visual/behavioral differences. Use when a feature was built from a design and needs verification, or when design and implementation drift.
- implement-from-design
- Implement a UI from a Figma design: fetch design context, map to the project's framework and design system, and verify against the design. Use when the user provides a Figma link and asks for the implementation.
- inspect-design-context
- Extract design context from a Figma file through the official Figma MCP: design tokens, variables, components, and layout structure for a selected frame or node. Use when implementing a design, checking design tokens, or understanding a Figma screen's structure.
- map-design-components
- Map the components in a Figma file to the project's code components: identify reusable components, their properties, and where they are used. Use when building a design system, checking component coverage, or planning which components to extract or reuse.
Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.
MCP servers · 1
- figmastreamable-http
- https://mcp.figma.com/mcp
Read from the plugin's own mcp.json. We list environment variable names, never values.
Category
Design & Frontend. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.
Keywords
figma · design · design-tokens · components · mcp · agent-plugins
Related by publisher and keywords
Inspect and debug Cloudflare: Workers, DNS, request handling, and configuration, via Cloudflare's official Code Mode MCP server.
Current library and framework documentation via Context7's first-party MCP server, with usage-discipline skills for when an agent should consult it.
Search, scrape, crawl, and extract from the web with Firecrawl's official MCP server, with focused workflow skills.
Inspect and work with GitHub: pull requests, issues, CI, and repositories via GitHub's official MCP server, with focused workflow skills.
Inspect and diagnose Kubernetes clusters: pods, resources, events, logs, and health, via a trusted read-only Kubernetes MCP server plus workflow skills.
Research and summarize a Notion workspace: find pages, gather context, and prepare project updates, via Notion's official hosted MCP server.
[](https://agentpluginsdirectory.com/plugins/figma--hiai-gg)✓ Verified . We fetched the manifest from GitHub and checked it against the official Agent Plugins 1.0.0 schema at agent-plugins.org.