New Member

Figma's approach breaks the core promise of MCP

Forum|Forum|5 months ago
April 1, 2026
20 replies
5517 views

The Figma MCP server fails to authenticate when using opencode, returning a 403 Forbidden error.

To Reproduce
1. Configure Figma MCP in opencode.json:

{
"mcp": {
"figma": {
"type": "remote",
"url": "https://mcp.figma.com/mcp",
"enabled": true,
"oauth": {}
}
}
}

2. Run: opencode mcp auth figma

3. Error received: HTTP 403: Invalid OAuth error response: SyntaxError: JSON Parse error:
Unexpected identifier "Forbidden". Raw body: Forbidden

Expected behavior
OAuth authentication should succeed, as it does with other MCP servers like Context7, Sentry, etc.

Root cause
According to Figma's documentation (https://help.figma.com/hc/en-us/articles/32132100833559), Figma only supports a pre-approved allowlist of MCP clients:
- Claude Code ✓
- Cursor ✓
- VS Code ✓
- Codex ✓
- etc.

OpenCode is not on this list, so Figma's authorization server rejects the OAuth flow.

Discussion

Figma's approach breaks the core promise of MCP - that any client should work with any server. This creates vendor lock-in and limits the ecosystem.

This appears to be an architectural issue with Figma's MCP implementation - they're treating MCP like a proprietary API rather than following the protocol's interoperability standard. Other MCP servers (Context7, Atlassian, AWS, Sentry, etc.) work fine with OpenCode.

Show previous replies

David Call

New Member

@Jaycee Lewis What’s the ETA on opencode approval? Looks like Claude, Cursor, and Codex are all at the table. How much longer will the OC community be waiting?

David Call

New Member

@Celyn_L Would you please post some status on where we’re at with opencode mcp access? This seems like it should be a no brainer to get it on the list.

Stein Olav Pettersen

New Participant

Seems like OpenCode are working on something 🤞🤞🤞

https://github.com/anomalyco/opencode/issues/988

David Call

New Member

You just made my whole morning @Stein Olav Pettersen 😁

Celyn_L

Figmate

Hi everyone, thanks so much for taking the time to share your feedback and letting us know how important OpenCode MCP support is to your workflows.

I've passed your feedback along to the team, and I want to assure you that they've heard your requests and are actively working on it. While I don't have an ETA or any updates to share just yet, I really appreciate everyone continuing to share their feedback and use cases.

Thanks again for your patience in the meantime 🙏

Vitali Zinkevich

New Member

+1 from me as well.

I ran into the exact same issue today while trying to connect the Figma remote MCP server from OpenCode (opencode mcp auth figma). The OAuth flow fails with a 403 Forbidden, while other remote MCP servers authenticate without any problems.

OpenCode is becoming a popular choice for developers, and having it included in the Figma MCP allowlist would make a big difference.

Celyn_L

Figmate

Hi @Vitali Zinkevich and everyone following this thread, thanks for flagging this and for your interest in using OpenCode with Figma's MCP server.

I’ve checked in with our team, and there are still a few steps that require coordination with the OpenCode team before access can be enabled. Our team has been trying to connect with them to help move this forward.

If you happen to be in contact with someone from the OpenCode team, you’re welcome to let them know that the Figma team is trying to help unblock this, and it would be great if they could respond to us or get in touch.

Thanks again for raising this with us and for your support in getting OpenCode connected!