fix(figma): deploy to the figma-mcp site; figma belongs to another project
Why
After #558 merged, https://sites-figma.deco.site/mcp answers 404 straight from Cloudflare, so the request never reaches the cluster. The site name figma was already taken: it is an unrelated deco storefront (deco-sites/figma, domain figma.deco.site, in another workspace). deploy.json pointed this MCP at that site, so the MCP never got a site of its own.
What
deploy.json:"site": "figma"โ"site": "figma-mcp".figma/app.jsonandregistry.json: the connection URL becomeshttps://sites-figma-mcp.deco.site/mcp.figma/README.mdand.env.example: the new URL and the new OAuth callback,https://sites-figma-mcp.deco.site/oauth/callback.
I checked that figma-mcp is free: there is no sites-figma-mcp.deco.site or figma-mcp.deco.site, and no deco-sites/figma-mcp or decocms/figma-mcp repo.
After merge
- The
figma-mcpsite needsFIGMA_CLIENT_ID,FIGMA_CLIENT_SECRETandOAUTH_STATE_SECRET. The env vars that were set on the storefrontfigmasite are being removed from it. - The Figma OAuth app's redirect URL changes to the new callback.
- The
deco/figmaregistry entry needs the new URL. - @JonasJesus42: with the registry publish step failing since late September, how does a new kubernetes-bun site get created and built now? Is it the same way
dynamic-yieldwent live?
๐ค Generated with Claude Code
Summary by cubic
Fixes the Figma MCP deployment so requests reach the cluster instead of 404ing at the edge. The site name figma was already taken by an unrelated deco storefront, so the MCP now deploys to the figma-mcp site at https://sites-figma-mcp.deco.site/mcp.
Migration
- Points
deploy.jsonat thefigma-mcpsite and updates the connection URL and OAuth callback inapp.json,registry.json,README.md, and.env.example. - After merge, set
FIGMA_CLIENT_ID,FIGMA_CLIENT_SECRET, andOAUTH_STATE_SECRETon thefigma-mcpsite and remove them from thefigmastorefront. - Update the Figma OAuth app's redirect URL to
https://sites-figma-mcp.deco.site/oauth/callback.