Plugin or Connector? Connecting Figma to Claude Cowork

Connecting Figma to Claude looks like one switch in Settings. It isn't — the answer turns on two words the app puts side by side, plugin and connector, and one leftover command.

A connector is the link to one outside service: an MCP server, plus your sign-in. Plug it in, and Claude gets that service's tools and data — think Google Drive, GitHub, Microsoft 365. A plugin is a package you install — it can bundle skills, agents, hooks, slash commands, and one or more connectors. The connector is the cable; the plugin is the kit box, cable inside, plus the manuals. The Figma plugin page lists fourteen skills and one connector.

Bear's first stop was Customize, then Connectors — search figma, and it's there, provided by the Figma plugin, but the status column says "connects in sessions," no button, while GitHub and Microsoft 365 right below it have Connect buttons. That page can't sign Figma in. Opening the plugin showed the same dead end: connector not added, Connect greyed out. The session's MCP servers panel was worse — Vercel had a Connect button, Figma had no row at all.

The cause was a leftover: Bear had earlier run claude mcp add at user scope for a server named figma at mcp.figma.com — the same address the plugin's own server uses. Two servers, one address, and the bare one shadowed the plugin's. The fix: remove the leftover with claude mcp remove figma -s user, quit and reopen the desktop app, then open the MCP panel in a session — now there's a row: figma, provided by the Figma plugin, with a working Connect button. Connect, allow access, checkmark. Figma's whoami then returned the right team, and Claude could read the FigJam board.

"Connects in sessions" means exactly that: a plugin's server is signed in from a session's MCP panel, not from account-level Settings. An account connector, the kind with a Connect button in Settings, is signed in once and works across chat, the desktop app, and Cowork — Figma has one of those too, but per Figma's own help page it currently supports FigJam only; the plugin brings the full server, with design context and canvas writes, plus fourteen skills.

One caveat: on Team and Enterprise plans, an Owner has to enable a connector first, so a greyed-out Connect on a university account may be a setting, not a bug.

Your Turn: Paste into Claude Code: "List every MCP server and plugin in my Claude setup, and flag any two that point at the same address." Then check two things yourself: which Claude account you're signed into, and whether the MCP panel shows one Figma row — not zero, and not two.

Sources: Figma, "Claude Code and Figma: Set up the MCP server"; "Create FigJam diagrams with Claude"; "Guide to the Figma MCP server" (help.figma.com). Claude, Figma connector (claude.com/connectors/figma). Claude Code, Plugins (code.claude.com/docs/en/plugins). Claude Help Center, "Use connectors to extend Claude's capabilities" (support.claude.com). Every factual claim in this video was checked against these sources before rendering. An independent series, not affiliated with or endorsed by Figma or Anthropic.

0:00 The question 0:11 Connector vs plugin 0:59 The wrong turn: Connectors 1:15 The dead end 1:27 The cause: a leftover server 1:42 The fix 2:09 What "Connects in sessions" means 2:23 Figma's account connector 2:38 Two accounts, one Figma 2:55 Recap 3:13 Your turn

Series: Figma for Educational AI. @NikBearBrown

Deliberately Not Claimed

This video is an independent production, not affiliated with or endorsed by Figma or Anthropic. It walks through one specific troubleshooting case on one account setup and does not claim every Connect-button issue has this same cause, or that Figma's account-connector FigJam-only limitation will remain unchanged. Whether the greyed-out button in Settings itself would have activated after the fix was not verified — the confirmed fix came through the session's MCP panel. Check the linked sources for current, authoritative setup steps.

Production Credits

Fully AI-generated production — no human-performed audio or video.

Narration: Liam (Kokoro am_onyx) Animation & motion graphics: Manim, Remotion Credit line: @NikBearBrown Hashtags

SEO Keyword Tags

Figma Claude Connect greyed out, Claude Cowork Figma, Claude plugin vs connector, claude mcp remove, Figma MCP troubleshooting, Claude Code plugins, MCP server duplicate address, Figma connects in sessions, Claude connectors settings, Figma plugin Claude, Claude desktop app Figma fix, Claude Enterprise connector, Figma FigJam Claude connector, Claude Team connector permissions, MCP panel troubleshooting

What this video covers

• 0:00 — The question 0:11 Connector vs plugin 0:59 The wrong turn: Connectors 1:15 The dead end 1:27 The cause: a leftover server 1:42 The fix 2:09 What "Connects in sessions" means 2:23 Figma's account connector 2:38 Two accounts, one Figma 2:55 Recap 3:13 Your turn

Transcript

A lightly formatted transcript of the video, with timestamps so you can jump to any section on YouTube.

The question 0:11 Connector vs plugin 0:59 The wrong turn: Connectors 1:15 The dead end 1:27 The cause: a leftover server 1:42 The fix 2:09 What "Connects in sessions" means 2:23 Figma's account connector 2:38 Two accounts, one Figma 2:55 Recap 3:13 Your turn

[0:00] Moni, this is Liam in for Bear. Bear asked a simple question, how do I connect Figma to Claude work? The answer turned on two words the app put side by side, plug-in and connector, and one leftover command. Most people think connecting Figma is one switch in settings. It's a plug-in signed in from a session. Mix up the two words and you'll hunt for a button in the wrong place. Bear did. A connector is the link to one outside service, an MCP server plus your sign-in. Plug it in and Claude gets that service's tools and data. On Bear's screen, Google Drive, GitHub, Microsoft 365. A plug-in is a package you install. It can bundle skills, agents, hooks, {slash} commands, and one or more connectors. The connector is the cable. The plug-in is the kit box with the cable inside plus the manuals. Bear's screens show it. The Figma plug-in page lists 14 skills and one connector. And when his terminal reloaded plug-ins,

It counted the parts: two plug-ins, five skills, nine agents, four hooks, two plug-in MCP servers. His first stop was customized then connectors. Search Figma and there it is provided by the Figma plug-in, but the status column says connects in sessions. No button. Right below, GitHub and Microsoft 365 have connect buttons. This page can't sign Figma in. So, he opened the plug-in, its connector Figma not added. Click through, not connected yet, and the connect button is grayed out. The sessions MCP servers panel was worse. Versal had a connect button. Figma had no row at all. The cause was a leftover. Earlier, Bear had run Claude MCP add at user scope for server named Figma at mcp.figma.com. That's the same address the plug-in server uses. Two servers, one address, and the Bear one shadowed the plug-in's. The fix, remove the leftover. Claude MCP remove figma-s user. Quit the desktop app and reopen it. Open the MCP panel in a session and now there's

A row, Figma provided by the Figma plug-in with a connect button. Connect allow access check mark. From that session, Figma's who am I returned to student tier team and Claude read the lectern figjam board, not verified whether the grayed out button in settings lit up, too. The win came through the sessions panel. So, connects in sessions means exactly that. A plugin server is signed in from a sessions MCP panel. An account connector, the kind with a connect button, is signed in once on your Claude account and works across chat, the desktop app, and Cawork. Figma has an account connector, too. Settings, connectors, browse connectors, Figma connect. But, Figma's help page says that integration currently supports figjam only. The plugin brings the full server with design context and canvas rights, plus 14 skills. One caveat Bear insisted on, his terminal ran on his university's Claude enterprise account, the desktop app and Cawork on his personal Max account. Same Figma account either way.

On team and enterprise plans, an owner has to enable a connector first, so a grayed out connect at school may be a setting, not a bug. Let's recap with Claude. A connector is an MCP server plus your sign in. A plugin is the kit box that can carry one. Connects in sessions means you sign in from the sessions MCP panel. In the test, if connect is grayed out and you once ran Claude MCP at Figma, remove it and restart before you blame your admin. Your turn. Paste this into Claude code. List every MCP server and plugin in my Claude setup and flag any two that point at the same address. It's a duplicate hunt, and a duplicate is exactly what hit Bear's Figma row. Then, check two things yourself. Which Claude account are you signed into, and does the MCP panel show one Figma row, not zero, and not two? Plugin or connector connecting Figma to Claude Cawork at Nick Bear Brown.