We've been excited to integrate Figma MCP into our workflow to connect and update our design system via claude code, but ran into a significant wall: the remote MCP server at mcp.figma.com only works with a personal Anthropic Pro or similar account. We're required to use Claude Code via AWS Bedrock here, which is how many enterprise teams access Claude. Figma MCP does not support Bedrock or other enterprise auth paths.
We spent a couple of hours troubleshooting and found that those of us using the AWS bedrock keys can't use the MCP server setup that is documented. Instead, they have to:
- Install Node.js manually
- Create a background service (launchd plist) to run the MCP server locally
- Manually configure Claude Code to point to a local HTTP server on port 3333
- Debug port conflicts and token issues that the remote setup handles automatically
We don't have it fully working yet, but this is already a meaningful barrier for the teams who arguably need this integration most. Enterprise design orgs working on complex products with real design systems shouldn't have to do this.
We'd love to see native Bedrock and enterprise auth support for the remote MCP server, and official documentation for non-Pro claude setups. Even a clear acknowledgment that this is a known gap would help teams plan around it.
Thanks for considering it.
Jackie Curry