Figma MCP: generate_figma_design tool not available in Claude Code

[tanya-erm]

Summary

The Figma MCP server (mcp.figma.com/mcp) exposes the generate_figma_design tool to Claude.ai (browser) but not to Claude Code (CLI). This tool allows pushing code/designs into Figma — a key workflow for developers working locally.

Steps to reproduce

1. Add the Figma remote MCP server:

   claude mcp add --scope user --transport http figma https://mcp.figma.com/mcp

2. Authenticate successfully via /mcp
3. Try to use generate_figma_design — the tool does not appear in the available tool list

Available tools (Claude Code)

The server only exposes read-oriented tools to Claude Code:

• get_design_context, get_screenshot, get_metadata, get_variable_defs, get_figjam
• generate_diagram (FigJam Mermaid only)
• Code Connect tools (send_code_connect_mappings, get_code_connect_suggestions, etc.)

Expected behavior

generate_figma_design should be available in Claude Code, just as it is in Claude.ai browser. The MCP server URL is the same — there's no technical reason to gate this tool by client type.

Evidence

• Claude.ai browser successfully uses generate_figma_design to push screen designs to Figma (screenshot attached workflow: edit code → generate_figma_design → success)
• Community confirmation on Figma forum that this feature is not available through the Claude Code connector
• The same MCP endpoint is used by both clients

Impact

Developers using Claude Code (the primary desktop dev tool) cannot push designs to Figma, forcing them to context-switch to Claude.ai browser for this workflow. This is a significant gap for design-to-code and code-to-design iteration.

Note

This may be a Figma-side decision on which tools to expose per client, but raising here as well since Claude Code users are affected and Anthropic may be able to coordinate with Figma on enabling feature parity.

[LukLuz80]

+1 — Same issue here on Claude Code v2.1.76 (VS Code extension, Windows 11).

Setup: Official Figma MCP via claude.ai Figma connector (built-in) — Connected, authenticated, 12/13 tools available. generate_figma_design is the only missing tool.

Additional finding: Adding the Figma MCP manually (claude mcp add --transport http figma https://mcp.figma.com/mcp) creates a second server entry that shows "Needs authentication" but cannot authenticate — likely because the built-in connector already occupies the OAuth session for mcp.figma.com.

Key context: Figma's own documentation explicitly lists Claude Code as a supported client for generate_figma_design (see tools-and-prompts and code-to-canvas). The supported client list includes: Augment, Claude Code, Codex, Cursor, Factory, Firebender, VS Code, Warp.

This is a critical workflow gap for design teams using Claude Code for code ↔ Figma iteration.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.