Skip to main content
Tyler Herbert
New Member
Oct 23, 2026 12:48 PM UTC
Solved

Code Connect on the Professional plan: docs say it’s supported, but there’s no Code Connect token scope and mappings are rejected

Our team is on the Professional plan. I’m a member with a Dev seat. The Code Connect quickstart and help center both say Professional plans can use Code Connect with one active library and one active framework, so we tried to set it up for our design system library. Two things block us:

  1. No Code Connect scope: when I create a personal access token, Code Connect isn’t in the list of scopes. Without it, figma connect publish can’t run.
  2. Mappings rejected: saving a single mapping through the Figma MCP server (send_code_connect_mappings) returns: “Code connections can only be made in libraries that are in Organization or Enterprise plans.”

Our template files parse fine locally with the CLI (v2.0.2), so the setup itself looks right.

Is Code Connect actually available on Professional plans now? or are the docs wrong?

Celine_
Celine_Solution
Community Support
Oct 27, 2026 10:51 AM UTC

Hi Tyler, stepping in for ​@Jaycee Lewis here!
I am sharing the clarification our Technical Quality team sent you here too, for anyone with a similar question. We understand you are seeing the message "Code connections can only be made in libraries that are in Organization or Enterprise plans." when creating a connection with the Figma MCP.
 

On the Professional plan, creating Code Connect connections with MCP is not supported at this time. You can create connections through the Code Connect UI or the CLI for Professional teams. Figma MCP can then use those active connections, but it currently doesn’t support creating them.
You can also find more details about Code Connect for Professional plans in our Help Center article here.

Please also note your feedback has also been shared with our Product and Engineering teams to help make this distinction clearer in the documentation. Thank you again for flagging it and sorry for any confusion here!
(I’ve gone ahead and marked as solution my reply, so others can see the last update here.)

6 replies

Jaycee Lewis
Figmate
Figmate
Oct 23, 2026 10:06 PM UTC

Hey ​@Tyler Herbert 👋 Thanks for flagging. Can you share a screenshot of the scopes that you do see when creating your token, please? Do you have other scopes listed under Development?

Thanks for the additional details! — Jaycee

 

Tyler Herbert
New Member
Oct 26, 2026 1:38 PM UTC

Here are the scopes I see

Jaycee Lewis
Figmate
Figmate
Oct 26, 2026 10:52 PM UTC

Thank you ​@Tyler Herbert 🙌 I opened a support ticket for this. The ID is 2223728 and the email subject line is Code Connect unavailable on Professional plan — missing token scope and MCP mapping error. Please keep an eye on your inbox (and spam folder if necessary) for the email and any replies from our team. Thanks again! — Jaycee

Albert Vargas
New Member
Oct 24, 2026 6:51 PM UTC

​@Tyler Herbert I am also trying to figure if Pro mode actually supports Code Connect or not. I found different documentation. It looks like it only connects to one ui kit but it must be published? Is till haven’t found any documentation on actually connecting via CLI when on Pro. Following this in the hopes that support clarifies things up

adamsmasher
Figmate
Figmate
Oct 24, 2026 7:15 PM UTC

Thanks for your reply, ​@Albert Vargas, and great question. We cover plan differences in our help article on Code Connect, but to clarify for you here:

 

Professional plans can have one active library and one active framework, e.g. one repo with React components. You can use both Code Connect UI and the CLI, and setting up the CLI is pretty much the same for Professional.