New Member

Solved

Grok Bot / Cursor remote Figma MCP OAuth fails with HTTP 403 Forbidden (client allowlist?)

Forum|Forum|2 days ago
September 23, 2026
6 replies
94 views

Hi Figma team,

I'm trying to connect Figma's remote MCP server from Grok Bot (Cursor MCP connector) and OAuth fails before the authorize UI reliably opens.

Endpoint: https://mcp.figma.com/mcp
Client: Grok Bot / Cursor MCP connector (Windows)
Account: [email redacted by forum moderator to remove PII]
Team: “최진철의 팀” (Professional plan, Full seat)
Existing support ticket: #2145748

What happens
1. I add the remote MCP URL as documented for “other agents”:
{ "mcpServers": { "Figma": { "url": "https://mcp.figma.com/mcp" } } }
2. The connector registers, but stays in needsAuth / authentication_required with 0 tools.
3. Connect / auth attempt returns HTTP 403 Forbidden.
4. Response body is plain text "Forbidden" (not JSON).
5. The Figma OAuth consent UI often never appears.

What I already ruled out
- Seat / plan alone: Full seat on a Professional team.
- File Share permission: this fails at OAuth / connector edge before any file tool call.
- Desktop local MCP (http://127.0.0.1:3845/mcp): not applicable here because Grok Bot's URL connector does not run on the same machine as Figma desktop.
- Remove / re-add of the connector and force reauth: same 403.

This looks similar to the OpenCode / Dynamic Client Registration allowlist discussion:
https://forum.figma.com/report-a-problem-6/figma-s-approach-breaks-the-core-promise-of-mcp-52507

Ask
Please allowlist / register the Grok Bot (Cursor) MCP client_name for https://mcp.figma.com/mcp, or tell us the exact client registration requirements so this connector can complete OAuth.

Happy to share HAR / screenshots / a screen recording, and I can grant view-only access to support-share@figma.com if needed.

Thanks!

Best answer by Celine_

Hey @최진철 , Celine from the Figma Community Support team here! Thank you for sharing these detailed report! I was able to see your ticket #2145748, and our Technical Quality team is currently investigating the issue. For visibility, the team is waiting some additional information from you to continue the investigation. Please check the inbox associated with your support case and reply directly there when you can 🙏🏼

For visibility, the specialist confirmed that because the connection returns an HTTP 403 before the OAuth flow opens, they’re checking with our MCP team to determine what’s happening during the authentication request.

Please continue the conversation through your support case, as the team there is best equipped to review the technical details and provide further updates. Thank you for your patience while they investigate!

Celine_Answer

Community Support

Hey @최진철 , Celine from the Figma Community Support team here! Thank you for sharing these detailed report! I was able to see your ticket #2145748, and our Technical Quality team is currently investigating the issue. For visibility, the team is waiting some additional information from you to continue the investigation. Please check the inbox associated with your support case and reply directly there when you can 🙏🏼

For visibility, the specialist confirmed that because the connection returns an HTTP 403 before the OAuth flow opens, they’re checking with our MCP team to determine what’s happening during the authentication request.

Please continue the conversation through your support case, as the team there is best equipped to review the technical details and provide further updates. Thank you for your patience while they investigate!

Vincent Koopmans

New Member

I have the exact same issue right now. not with Grok but trying to get the Figma plugin working.

aazzzz

New Member

Yes I’m having the same issue right now. can’t logout with figma mcp and also can’t login in cursor. please fix this ASAP. thanks

Celine_

Community Support

Hey @Vincent Koopmans , @aazzzz , thanks for flagging this and sorry to hear you are also having issues! For @최진철 case, I can confirm this is still under active investigation on our end.

In the meantime, it would be really helpful if you could also submit a bug report so our team can look into what's happening specifically on your end. The more reports we have with individual details, the better equipped the team will be to investigate.

To submit: go to the Support Hub / Type “Report a bug” / Click Start a chat and select Enter and follow the prompt.

Then, in the form, please include:

Your MCP client (Grok Bot / Cursor or other)
The exact error message you're seeing
Any screenshots or screen recordings of the issue

Thank you 🙏

m.politanskyi

New Member

Hi there, I have the same issue

MCP client (Cursor)
The exact error message:
2026-09-25 19:06:47.510 [info] [V2] Handling CreateClient action

2026-09-25 19:06:47.510 [info] [V2 FSM] connection:connect_start: conn=idle,auth=unknown -> conn=connecting,auth=unknown

2026-09-25 19:06:47.847 [info] MCP OAuth provider initialized

2026-09-25 19:06:48.520 [info] Successfully connected to streamableHttp server

2026-09-25 19:06:48.520 [info] [V2 FSM] connection:connect_success: conn=connecting,auth=unknown -> conn=connected,auth=unknown

2026-09-25 19:06:48.520 [info] CreateClient completed, connected: true, statusType: connected

2026-09-25 19:06:48.724 [warning] MCP HTTP exchange completed
Any screenshots or screen recordings of the issue:

Nashwan Abdullah

New Member

I have the same issue.

Sign up

Login with SSO

Login to the community

Login with SSO