Skip to main content
monjeyer
monjeyer
New Member
Oct 15, 2026 8:08 PM UTC
Question

Figma MCP connector allows only one Claude account per Figma account (bug report)

I use Claude on two separate Claude accounts, and both need the Figma MCP connector pointed at the same Figma account. This does not work. As soon as I authorize the Figma connector on the second Claude account, the first one is invalidated and its Figma tools stop working (“The user’s connection to this connector was invalidated”). Re-authorizing on the first account then kicks off the second.

The same Figma login can be authorized in Claude Code’s own Figma plugin at the same time without conflict, so the limit seems to be one active authorization per Figma account for the Claude connector client, rather than a general one-session rule. Please allow one Figma account to hold more than one active authorization for the same MCP client, or document the limit and the intended workaround. Reproduced October 13, 2026 on the current remote server at mcp.figma.com with two Claude accounts, one Figma account.

My original report was categorized as Suggest a Feature. I am reporting this as a bug because authorizing another account invalidates an existing working connection. Is invalidating an existing authorization expected behavior? If not, please treat this as a bug. If it is, please explain the restriction and supported workaround.

Original report: https://forum.figma.com/suggest-a-feature-11/figma-mcp-connector-allows-only-one-claude-account-per-figma-account-58945

3 replies

Jaycee Lewis
Figmate
Jaycee Lewis
Figmate
Oct 16, 2026 10:32 PM UTC

Hey ​@monjeyer 👋 Thanks for your follow up. I took this to my resources to get us clarity. I’ll post back here when I have more info for us. Have a great weekend! — Jaycee

Jaycee Lewis
Figmate
Jaycee Lewis
Figmate
Oct 20, 2026 4:23 AM UTC

Hi ​@monjeyer 👋 I have an update for us:

Authorizing the same Figma account through another Claude connection can replace the earlier authorization and disconnect the first connection. We’re working on better support for multiple simultaneous connections. For now, reconnecting one may disconnect the other.

Thanks again for flagging this. — Jaycee

Validatus.com
Validatus.com
New Member
Nov 8, 2026 6:30 AM UTC

Hi ​@monjeyer 👋 I have an update for us:

Authorizing the same Figma account through another Claude connection can replace the earlier authorization and disconnect the first connection. We’re working on better support for multiple simultaneous connections. For now, reconnecting one may disconnect the other.

Thanks again for flagging this. — Jaycee


Good day ​@Jaycee Lewis - Thanks for pointing this out!
 

The issue is reproducible for chatGPT: ChatGPT A and Codex can access the same Figma account simultaneously. Connecting ChatGPT B invalidates ChatGPT A, and vice versa.

ChatGPT A ──┬──> Figma ✓
Codex     ──┘

ChatGPT A ──X── ChatGPT B
           │
       Same Figma
       OAuth user

This suggests an OAuth token/grant collision between ChatGPT accounts as well.

Expected: Independent, concurrent OAuth grants per ‘GPT’ account without mutual invalidation.

Can Figma confirm whether a fix is planned?
Thanks so much!

Terms & ConditionsAccessibility statement