figma-to-markdown-mcp

figma-to-markdown-mcp

Converts Figma to Markdown. Strips out visual noise to drastically reduce LLM token consumption.

Category
访问服务器

README

figma-to-markdown-mcp

npm version License: MIT CI

A compact markdown layer in front of Figma MCP for AI implementation workflows.

This MCP server accepts a Figma node URL, calls Figma Desktop MCP get_design_context internally, and returns compact markdown — stripping out raw React/Tailwind passthrough that inflates token cost without adding implementation value.

~45% token reduction on typical design context payloads (sample: 1,053 → 582 tokens).


How It Works

User  →  implementation request + Figma node URL
      →  figma-to-markdown MCP
      →  Figma Desktop MCP  (get_design_context + get_metadata)
      →  compact markdown
      →  implementation agent

The compact output keeps what matters for implementation:

Kept Removed
Source metadata Raw React/Tailwind passthrough
Node name, type, frame Repetitive wrapper boilerplate
Layout and spacing spec Verbose class attribute dumps
Text and typography facts
Asset references
Implementation notes

Requirements

  • Figma Desktop app running
  • Dev Mode MCP enabled in Figma Desktop settings
  • The document containing the requested node must be the active tab
  • Node.js 18 or later

Installation

No install step required. Use npx and it runs on demand:

npx figma-to-markdown-mcp

Or install globally if you prefer:

npm install -g figma-to-markdown-mcp

Registration

Register the server in your MCP client's config file. The JSON format is the same across clients — only the file location differs.

Claude Desktop

Config file: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "figma-to-markdown": {
      "command": "npx",
      "args": ["-y", "figma-to-markdown-mcp"]
    }
  }
}

Claude Code

Config file: .claude/settings.json (project) or ~/.claude/settings.json (global)

{
  "mcpServers": {
    "figma-to-markdown": {
      "command": "npx",
      "args": ["-y", "figma-to-markdown-mcp"]
    }
  }
}

Cursor

Config file: .cursor/mcp.json

{
  "mcpServers": {
    "figma-to-markdown": {
      "command": "npx",
      "args": ["-y", "figma-to-markdown-mcp"]
    }
  }
}

Codex CLI

Config file: ~/.codex/config.toml (global) or .codex/config.toml (project)

[mcp_servers.figma-to-markdown]
command = "npx"
args = ["-y", "figma-to-markdown-mcp"]

Usage

Once registered, give your agent a Figma node URL and ask for an implementation.

Agent flow:

  1. User sends a Figma node URL with an implementation request.
  2. Agent calls get_design_context_compact with the URL.
  3. This server fetches design context from Figma Desktop MCP internally.
  4. Raw output is compacted into markdown and returned.
  5. Agent implements from the compact markdown.
  6. Only if facts are missing should the agent fall back to raw Figma MCP tools.

Tool: get_design_context_compact

{
  "figma_url": "https://www.figma.com/design/FILE_KEY/Name?node-id=123-456",
  "include_stats": false
}
Parameter Type Required Description
figma_url string yes Full Figma URL including node-id query parameter
include_stats boolean no Append token size statistics to the output

Example output:

# Figma Design Context

## Source
- provider: `figma-mcp`
- transformed-by: `figma-to-markdown`
- node-id: `123:456`
- file-key: `ExampleFileKey123`
- mode: compact implementation handoff

## Node Summary
- component: `BasicNavi`
- type: `instance`
- frame: `375 x 48`

## Compact Element Spec
- `basic navi` → flex, items center; bg `#f6f6f6 (neutral/100)`
- inner content row → flex, flex `1 0 0`, gap `8px`; px `10px`, py `4px`

## Text Spec
- text "Label" → font `Pretendard Regular`, size `19px`, line `24px`, color `neutral/900`

Notes

  • file-key is extracted from the input URL for traceability.
  • get_metadata is fetched in parallel as a supplement and will not fail the main request if unavailable.
  • When compaction confidence is low, the output includes a ## QA Flags section.
  • Raw upstream code is omitted by default. Set include_stats: true to see payload size.

Version & License

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选