HTTP 405 on Figma MCP

Description

Tried to use figma MCP server (remote using https://mcp.figma.com/mcp) but when connecting it returns a 405 Method not Allowed error and does not authenticate. Has anyone been able to configure this MCP successfully?

OpenCode version

v1.0.163

Steps to reproduce

Run opencode with this configuration:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "figma-mcp": {
      "type": "remote",
      "url": "https://mcp.figma.com/mcp",
      "enabled": true
    }
  }
}

Then figma MCP won't appear enabled, showing a HTTP SSE error: 405

Screenshot and/or share link

No response

Operating System

macOS 26.0.1

Terminal

Alacritty

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

[FEATURE]: Support MCP servers that require POST-based or non-standard SSE handshake #5371: [FEATURE]: Support MCP servers that require POST-based or non-standard SSE handshake - This feature request directly addresses the 405 Method Not Allowed error you're encountering with Figma MCP, as it's requesting support for POST-based MCP connections instead of the standard GET+SSE flow.
Issue with MCP and config #1720: Issue with MCP and config - Another user reported MCPClientError with Figma MCP configuration, though in a local setup context.
Figma MCP access #3984: Figma MCP access - Mentions the Figma MCP has authentication/whitelisting requirements.

Feel free to ignore if none of these address your specific case.

We need to be approved by figma to use their mcp so maybe that's the issue? I think we are in hte midst of the approval process rn

Any updates on that? Still HTTP 405 😢
If I try to use opencode mcp auth figma, it does not work as well, it says "dynamic client registration failed: http 403".

Yeah I think OpenCode still needs whitelisting by Figma, I'm hoping someone has sent off a request 🤞

#3875 (comment)

still waiting on approval

Is there any chance to allow custom MCP client names? From what I understand, this looks like a simple whitelist check. If the name can be customized to something like Cursor or Claude Code or whatever, would that bypass the restriction?

Honestly, I think what Figma is doing here is basically bullying.

@StereoApp You can try this in the meantime https://github.com/connorads/opencode/tree/mcp-auth-workaround?tab=readme-ov-file#mcp-auth-workaround

@StereoApp You can try this in the meantime https://github.com/connorads/opencode/tree/mcp-auth-workaround?tab=readme-ov-file#mcp-auth-workaround

Thanks, works for me.

any update here?😳

^

need approval from figma folks

Someday an engineer working on figma would see this, and then only opencode would have authorisation.

any update anyone? 😳

It's surprising that Figma is taking months to approve a new client, especially a popular one like OpenCode.

Do we have a confirmation from Figma that they're still reviewing it?

I also noticed there's an official request form at https://www.figma.com/mcp-catalog/ → Want remote server access? → Join the waitlist. It might be worth trying again through that channel if we haven't.

@connorads

@StereoApp You can try this in the meantime https://github.com/connorads/opencode/tree/mcp-auth-workaround?tab=readme-ov-file#mcp-auth-workaround

Thank you very much @connorads , it worked for me as well.

// ~/.config/opencode/opencode.json

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

Workaround without installing a fork: #988 (comment)

I reached out to Figma support about this. Summarizing what the support agent said:

Adding support for a new tool like OpenCode is non-trivial; it requires back and forth, establishing proper protocols, and ensuring the integration works reliably with Figma's design data, variables, components, etc.
He submitted an internal request and says there's some interest in supporting OpenCode, but no timeline; the team is not ready to do so right now
I asked if there was anything that could be done on the OpenCode side to make this easier; he said he didn't know, and their product/engineering team would need to evaluate

I'm probably going to be unfair and conspiratorial, but the fact that there's been so much delay in supporting OpenCode might be due to Figma's relationship with Claude/Claude Code.

Basically, all workarounds works perfectly and having an official Figma MCP integration for me is just for the sake of "not using a hack to solve a problem".

They are not being honest. Adding support to a new MCP client is trivial. In fact, they shot themselves in the foot as they implemented a whitelist on their backend side that just checks the client-provided client name string during client registration. If they hadn't done that there would be automatic support for any MCP client.
OpenCode with Figma MCP works perfectly fine if you provide "Claude Code (figma)" as the client_name

I tried pprotas's solution, but found that FigmaMCP only has read capability without write functionality. When I attempted to use Codex for impersonation, I discovered that a successful write operation could only be performed in opencode using Figma's write capability after sending a genuine write request through the actual Codex client.

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Navigation Menu

Repository navigation

HTTP 405 on Figma MCP #5636

Description

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

HTTP 405 on Figma MCP #5636

Description

Description

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Activity

github-actions commented on Dec 16, 2025

rekram1-node commented on Dec 16, 2025

HicaroD commented on Jan 3, 2026

connorads commented on Jan 3, 2026

rekram1-node commented on Jan 3, 2026

finnzio commented on Jan 6, 2026

connorads commented on Jan 6, 2026

finnzio commented on Jan 6, 2026

franvillasil commented on Jan 27, 2026

newideas99 commented on Feb 6, 2026

rekram1-node commented on Feb 6, 2026

JairajSustained commented on Feb 13, 2026

mamanico1 commented on Feb 20, 2026

frosas commented on Feb 22, 2026

OrRosenblatt commented on Feb 26, 2026

pprotas commented on Mar 9, 2026

mmirus commented on Mar 19, 2026

HicaroD commented on Mar 19, 2026

pprotas commented on Mar 19, 2026

Yink-Design commented on Apr 29, 2026

github-actions commented on Jul 3, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions