An unexpected interruption occurred during the Figma MCP call. #6436

Open
opened 2026-02-16 18:04:12 -05:00 by yindo · 5 comments
Owner

Originally created by @fguizc on GitHub (Jan 16, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

When using glm4.7 and invoking the Figma MCP in Plan mode, an error is reported, but no further error details are displayed on the interface.

Additionally, the API Key I am using is for the GLM China Mainland region's code plan package.

Plugins

oh-my-opencode

OpenCode version

1.1.23

Steps to reproduce

No response

Screenshot and/or share link

Image

Operating System

No response

Terminal

wrap

Originally created by @fguizc on GitHub (Jan 16, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description When using glm4.7 and invoking the Figma MCP in Plan mode, an error is reported, but no further error details are displayed on the interface. Additionally, the API Key I am using is for the GLM China Mainland region's code plan package. ### Plugins oh-my-opencode ### OpenCode version 1.1.23 ### Steps to reproduce _No response_ ### Screenshot and/or share link <img width="2596" height="1284" alt="Image" src="https://github.com/user-attachments/assets/fb7a36fd-2467-40e2-8367-c6f08cc5de14" /> ### Operating System _No response_ ### Terminal wrap
yindo added the bug label 2026-02-16 18:04:12 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 16, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #8102: 🐛 Bug Report: MCP Tool JSON Parsing Errors on OpenCode (GLM-4.7) - Reports similar MCP tool call errors with GLM-4.7, though focused on JSON parsing
  • #8431: GLM 4.7 AI_JSONParseError - Another GLM 4.7 issue with JSON parsing during tool calls

The root cause may be related to how OpenCode handles GLM-4.7 model responses when calling MCP tools. You might find solutions or workarounds discussed in those issues.

Feel free to ignore if your specific case differs from these.

@github-actions[bot] commented on GitHub (Jan 16, 2026): This issue might be a duplicate of existing issues. Please check: - #8102: 🐛 Bug Report: MCP Tool JSON Parsing Errors on OpenCode (GLM-4.7) - Reports similar MCP tool call errors with GLM-4.7, though focused on JSON parsing - #8431: GLM 4.7 AI_JSONParseError - Another GLM 4.7 issue with JSON parsing during tool calls The root cause may be related to how OpenCode handles GLM-4.7 model responses when calling MCP tools. You might find solutions or workarounds discussed in those issues. Feel free to ignore if your specific case differs from these.
Author
Owner

@rekram1-node commented on GitHub (Jan 16, 2026):

Our client isn't authorized yet for figma mcp so until that happens youll have issues

@rekram1-node commented on GitHub (Jan 16, 2026): Our client isn't authorized yet for figma mcp so until that happens youll have issues
Author
Owner

@fguizc commented on GitHub (Jan 16, 2026):

Our client isn't authorized yet for figma mcp so until that happens youll have issues

Understood. To add, it does not occur consistently; for me personally, it can be considered an intermittent issue. After all, I successfully called the Figma MCP multiple times on 15/01/26 to complete the development work. If you require more detailed logs or similar documents, I would be glad to provide them.

@fguizc commented on GitHub (Jan 16, 2026): > Our client isn't authorized yet for figma mcp so until that happens youll have issues Understood. To add, it does not occur consistently; for me personally, it can be considered an intermittent issue. After all, I successfully called the Figma MCP multiple times on 15/01/26 to complete the development work. If you require more detailed logs or similar documents, I would be glad to provide them.
Author
Owner

@fguizc commented on GitHub (Jan 16, 2026):

Our client isn't authorized yet for figma mcp so until that happens youll have issues

To further supplement, I am using the local Figma MCP instead of the remote one, which means that I have already installed the Figma Desktop application, and the address configured within the MCP protocol is also a local 172 address.

@fguizc commented on GitHub (Jan 16, 2026): > Our client isn't authorized yet for figma mcp so until that happens youll have issues To further supplement, I am using the local Figma MCP instead of the remote one, which means that I have already installed the Figma Desktop application, and the address configured within the MCP protocol is also a local 172 address.
Author
Owner

@fguizc commented on GitHub (Jan 16, 2026):

Our client isn't authorized yet for figma mcp so until that happens youll have issues

Based on my attempts, specific tool invocations tend to fail.

  • figma_get_design_context
  • figma_get_screenshot
Image Image
@fguizc commented on GitHub (Jan 16, 2026): > Our client isn't authorized yet for figma mcp so until that happens youll have issues Based on my attempts, specific tool invocations tend to fail. - figma_get_design_context ✅ - figma_get_screenshot ❌ <img width="1040" height="545" alt="Image" src="https://github.com/user-attachments/assets/8339ee6c-3178-4913-816e-c24658257342" /> <img width="2436" height="214" alt="Image" src="https://github.com/user-attachments/assets/b7cd7f8f-dd91-4d1c-94a4-bc0606763814" />
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6436