pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for io.github.GLips/Figma-Context-MCP

Pod holds 24 of 136 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to io.github.GLips/Figma-Context-MCP.

Most discussed

429 rate limit errors from Figma API

I have been getting this response all day, while trying to use the mcp with cursor: Error fetching file: Failed to make request to Figma API endpoint '/files/CSKFNNR9R6BynWVO2CvvpX/nodes?ids=8425:9830': Fetch failed with status 429: Too Many Requests

At first I thought the rate limit was on my API key by figma, but i'm able to do curls directly to figma's api using my api key. Does the framelink mcp specifically have rate limiting or is there rate limiting on mcp connections to figma?

Read the thread · 2025-11-23 · open · external user · 30 comments

0 tools enabled

Image

Title: MCP Server Connection Error Issue: 0 tools enabled

Issue Description The MCP server tip "0 tools enabled" in the Cursor editor.

Configuration Details

{
   "mcpServers": {
      "Framelink Figma MCP": {
         "command": "npx",
         "args": [
            "-y",
            "figma-developer-mcp",

Read the thread · 2025-07-09 · closed · external user · 12 comments

Tool mcp_Figma_get_figma_data not found

Image

Image

"Figma": {
  "command": "cmd",
  "args": [
    "/c",
    "npx",
    "-y",
    "figma-developer-mcp",
    "--figma-api-key=",
    "--stdio"
  ]
}

Read the thread · 2025-03-31 · closed · external user · 11 comments

get_figma_data not working

The get_figma_data tool started failing suddenly with the error:

{
  "content": [
    {
      "type": "text",
      "text": "Error fetching file: [object Object]"
    }
  ],
  "isError": true
}

This started happening with all selections and fails with selections that previously succeeded. It seems to be returning a 404 for any selection. Note, I am able to access the figma links on a browser and they have the appropriate permissions.

Read the thread · 2025-03-31 · closed · external user · 13 comments

Failed to connect server on Cursor

Image

Connect Timeout Error

but localhost:3333 is on

Read the thread · 2025-03-28 · closed · external user · 17 comments

MCP server fails to fetch Figma file data due to missing fetch in Node.js environment

Describe the bug When attempting to fetch Figma file data using the MCP server, the operation fails with the following error message: Error fetching file: Error: The MCP server is being run in a Node.js environment where fetch is not available. You won't be able to access any data related to the Figma file.

To Reproduce Steps to reproduce the behavior:

  1. Start the MCP server using Node.js
  2. Trigger a Figma-related action (e.g., fetching file or node)
  3. Observe the error in the consol

Read the thread · 2025-03-28 · closed · external user · 13 comments

MCP Server won't connect

I have a Windows 11 Lenovo 4060 laptop.

I've tried to connect the Figma MCP server to Cursor, but without luck.

I've noticed in the notes and in several videos, please have the button 'Add MCP Server' when they click on 'MCP' in settings.

I have a button that says 'Add new global MCP server'.

Can anyone help me get over this issue.

Image

![Image](https://github.com/user-attachments/assets/14fc10b3-7b26-4b

Read the thread · 2025-03-22 · closed · external user · 18 comments

Please update the Readme to let people know how to use this

Since the button to add new MCP takes us to a JSON, what should the settings be?

Read the thread · 2025-03-16 · closed · external user · 16 comments

Most recent

opencode 配置好figma的MCP之后，不能读取到figma的make文件嘛？

opencode 配置好figma的MCP之后，不能读取到figma的make文件嘛？这样的话该如何解决，好像只能读取到Desgin文件救命

Image

Read the thread · 2026-06-17 · closed · external user · 3 comments

No mcp tools to make designs?

I need two flows:

  1. prompt to design
  2. design to c++ code

looking at the available tools, i dont see any "create" "edit" "generate" tools to modify figma files. Image

Read the thread · 2026-06-06 · closed · external user · 1 comment

Feature request: expose image download/export support in the CLI

Hi! Thanks for building and maintaining this project.

As far as I can tell, the MCP server already supports downloading images/assets during tool usage, and the CLI also supports the fetch subcommand for retrieving design data directly.

Would you consider exposing the existing image download/export behavior through the CLI as well?

For example, something like:

figma-developer-mcp download-images \
  --file-key <fileKey> \
  --node-id <nodeId> \
  --format png
  --scale 2
  --image-

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/375) · 2026-05-03 · open · external user · 0 comments

### `download_figma_images` returns success, but no file is actually written to the local target

## Bug description

  `download_figma_images` returns success, but no file is actually written to the local target
  directory.

  The problem reproduces consistently in my environment for both:
  - bitmap/image nodes with valid `imageRef`
  - vector/SVG-capable nodes

  The tool reports success, and in one case even returns a full output path, but the target
  directory remains empty and the file cannot be found anywhere in the project.

  ---

  ## Environment

  - OS: Windows 11 Pro 10.0.2620

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/364) · 2026-04-24 · closed · external user · 0 comments

### 下载素材失败

1. 目录不存在
    - 目标目录提前手动创建成功
  2. 目录无写权限
    - 可手动写入测试文件 claude-write-test.txt
  3. 路径格式问题
    - 测试过 Windows 路径和 Unix 风格路径，结果一致
  4. 文件名问题
    - 测试过带扩展名、不带扩展名、短文件名，结果一致
  5. 节点选择错误
    - 位图节点含有效 imageRef
    - 矢量节点也可被工具接受

  预期结果
  - 返回成功时，目标文件应真实出现在 localPath 指定目录中

  实际结果
  - 工具返回成功，但文件未落盘到本地文件系统

  结论
  - download_figma_images 当前在该环境下存在“返回成功但不实际写入本地文件”的问题
  - 很可能是 MCP 服务端/桥接层仅回显成功，未真正写入当前机器，或写入发生在隔离环境中

  建议维护方排查
  1. localPath 是否真的映射到调用侧本地文件系统
  2. 返回成功前是否检查了文件真实存在
  3. Windows 环境下本地写入链路是否失效

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/363) · 2026-04-24 · closed · external user · 1 comment

### Late `notifications/progress` after tool response crashes stdio transport ("unknown progress token")

**Describe the bug**

`get_figma_data` calls intermittently cause the MCP client to close the stdio transport with a protocol error:

Connection error: Received a progress notification for an unknown token: {"method":"notifications/progress","params":{"progressToken":N,"progress":3, "total":4,"message":"Serialized, sending response"}} Closing transport (stdio transport error: Error) STDIO connection dropped after Ns uptime


The tool itself still reports `completed successfully`, but ever

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/362) · 2026-04-22 · closed · external user · 1 comment

### Getting 403 on FrameLink MCP call in claude code even though MCP shows as connected

Describe the bug
When using FrameLink MCP in Claude Code, all MCP tool calls return a 403 Forbidden error despite the MCP server appearing as connected in the client. The connection handshake succeeds and tools are listed correctly, but any actual tool invocation is rejected with a 403.
Software Versions

Figma Developer MCP: (run npx figma-developer-mcp --version and paste here)
Node.js: v22
NPM: 10
Operating System: MacOS Tahoe
Client: Claude Code
Client Version: 2.1.87

To Reproduce

Configur

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/358) · 2026-04-20 · closed · external user · 5 comments

### Telemetry error_message can include file keys and node IDs

## Summary

The telemetry rollout says Framelink sends anonymous usage data and that file IDs are not sent, but the current implementation still forwards raw `error_message` strings after only credential redaction. In practice, those messages can contain Figma file keys and node IDs.

This seems like a real contract mismatch rather than an intentional tradeoff:

- PR `#342` explicitly says "No Figma file contents, names, or IDs are sent as telemetry"
- current code still captures `error.message`

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/354) · 2026-04-16 · open · external user · 1 comment

### download_figma_images accepts symlinked localPath that escapes imageDir

## Summary

`download_figma_images` treats the configured `imageDir` as a write boundary, but the current path validation only compares lexical paths. If a child segment inside `imageDir` is a symlink to another directory, the tool accepts the path and the eventual write lands outside the configured boundary.

This looks like a real boundary bug rather than an intentional behavior change:

- `CONTRIBUTING.md` explicitly frames project-level config like `--image-dir` as part of the server boundar

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/353) · 2026-04-16 · closed · external user · 1 comment

### Failed to connect in Copilot cloud agent

I'm using Copilot cloud agent to do the AI workflow. It works 4 days ago, but it says connection closed. This is my setting. 

<img width="981" height="84" alt="Image" src="https://github.com/user-attachments/assets/e457c2df-22b5-466b-bd53-db022e2eca0d" />

![Image](https://github.com/user-attachments/assets/f8a830f1-9f17-4ba8-bca8-6dcb35bac6f4)

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/332) · 2026-04-07 · closed · external user · 2 comments

### SyntaxError: The requested module 'simple-xml-to-json' does not provide an export named 'default' (ESM compatibility)

## Environment:

* Node.js Version: v22.15.1
* Package: figma-developer-mcp
* Execution Command: npx -y figma-developer-mcp --figma-api-key=*** --stdio

## Describe the bug:
When running the MCP server via npx, it fails immediately with a SyntaxError. The issue stems from a downstream dependency @jimp/plugin-print attempting a default import from simple-xml-to-json, which appears to be incompatible with the current ESM execution environment.
## Error Trace:

[16:44]  Shell

Read the thread · 2026-04-05 · closed · external user · 4 comments

Security consideration: Indirect Prompt Injection via Figma design content

Hi @GLips,

While reviewing MCP server security across the ecosystem, I wanted to flag a consideration specific to Figma-Context-MCP's design content injection into LLM context.

The vector

When an LLM agent uses Figma-Context-MCP, text content from Figma designs is extracted and injected into the LLM context without sanitization. A malicious collaborator can embed prompt injection payloads in design elements that are invisible to human reviewers but fully processed by the LLM:

// Hidd

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/303) · 2026-03-23 · closed · external user · 4 comments

### --image-dir with drive root path fails due to double path separator in security check

When --image-dir is set to a drive root path (e.g., D:\, E:/, E:), the security path validation incorrectly rejects all non-empty localPath values due to a double path separator issue in the security check logic.

Invalid path: "project/src/static/images/test" resolves outside the allowed image directory. The server's image directory is "E:\". Provide a path relative to this directory (e.g., "public/images" or "assets/icons").

OS: Windows

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/300) · 2026-03-20 · closed · external user · 1 comment

### figma-developer-mcp fails on macOS ARM when run via npx due to sharp/libvips dlopen error

**Describe the bug**
On macOS ARM with Node 20, `npx -y figma-developer-mcp --stdio` fails with `sharp`/`libvips` ‘Could not load the "sharp" module using the darwin-arm64 runtime’ error.

**Software Versions**

- Node.js: v20.14.0
- NPM: 10.7.0
- Operating System: Mac OS 26.3/Darwin 25.3.0 (arm64)
- Client: Rovo Dev CLI
- Client Version: 0.13.54

**To Reproduce**
Run `npx -y figma-developer-mcp --figma-api-key=YOUR-KEY --stdio` from the command line

**Expected behavior**
See a successfully ini

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/288) · 2026-03-11 · closed · external user · 5 comments

### figma mcp Fetch failed with status 429: Too Many Requests

I juse config the mcp and get figma data from link of selection, and then it doesn't work any more

response message like:

Response Error fetching file: Failed to make request to Figma API endpoint '/files/xxx/nodes?ids=9243:34937': Fetch failed with status 429: Too Many Requests"

Is there someone who can tell me how to get around this rate limit?

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/287) · 2026-03-11 · closed · external user · 8 comments

### Security Request: Please bump `@modelcontextprotocol/sdk` and other dependencies to fix High severity vulnerabilities

Hello! Thank you for creating this amazing Figma MCP server.

I ran a security audit (`pnpm audit`) on the project and found 22 vulnerabilities, including 12 High-severity ones. Most of these are critical security flaws that were recently discovered and patched in the underlying dependencies.

For example, the current `@modelcontextprotocol/sdk` version in `package.json` (`^1.10.2`) is vulnerable to cross-client data leaks and ReDoS attacks (CVE-2025-27104, etc.). Anthropic has already released 

[Read the thread](https://github.com/GLips/Figma-Context-MCP/issues/281) · 2026-03-04 · closed · external user · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/GLips/Figma-Context-MCP/issues).