Skip to main content
RebecaAtida
New Member
Oct 2, 2026 8:54 AM UTC
Question

Can't generate MCP preview" on all components connected to self-hosted GitLab

Hi Figma team,

We're setting up Code Connect for our design system and the MCP preview in the Code Connect UI always shows "Can't generate MCP preview right now. Please try again later." It happens on every connected component.

Our setup:
- Code is hosted on a self-hosted GitLab instance (gitlab.atida.com), private repository.
- Components are connected at the component set level from the Code Connect UI, using the GitLab file URL (e.g. https://gitlab.atida.com/<group>/<project>/-/blob/main/src/components/Button/Button.tsx) and the exported component name (Button).
- We also published parserless Code Connect templates for the same components.
- The components show as "Connected", and the design context returned through the Figma MCP server includes the connected component correctly.
- We tried removing the local file-path connection and keeping only the GitLab one: same result.

Questions:
1. Does the Code Connect MCP preview support self-hosted GitLab repositories, or only repositories connected through the GitHub integration?
2. If GitLab isn't supported, is it on the roadmap, and is there a recommended alternative (e.g. Code Connect CLI, a GitHub mirror) to get the preview working?
3. Does the preview need the library to be published after the connection is made?

Plan: Organization

Thanks!
Rebeca Patiño
Atida

2 replies

Jaycee Lewis
Figmate
Figmate
Oct 2, 2026 7:57 PM UTC

Hey hey ​@RebecaAtida 🤩 Great questions. I took this to the MCP team t try to get your questions answered. I’ll follow up here if I get us an answer or if they have follow up question for us. Thank you — Jaycee

Jaycee Lewis
Figmate
Figmate
Oct 6, 2026 6:05 AM UTC

Hey ​@RebecaAtida I have some updates for us.

  • GitLab support: AI-generated MCP previews currently support connected GitHub repositories only. Self-hosted GitLab and enterprise/self-hosted GitHub aren’t supported. The preview error doesn’t affect the mappings sent through MCP. Your components can still show as Connected and provide context

  • Alternatives: GitLab isn’t currently supported. CLI-published templates are the supported alternative: when a published template is available, Figma uses it to render the snippet without generating a GitHub-based preview

  • Library publishing: The library’s design components must already be published, and mappings are shared with MCP immediately after connection.  Link to more info 

If you have any follow up questions, I am happy to take them back to my resources. — Jaycee