Question
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:
- No Code Connect scope: when I create a personal access token, Code Connect isn’t in the list of scopes. Without it,
figma connect publishcan’t run. - 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?
