Figma MCP: generate_figma_design tool not available in Claude Code

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:

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

1. Authenticate successfully via /mcp
2. 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.