Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Claude Code Bug Report: Figma MCP Tools Not Loading

Date: 2026-04-14
Claude Code Version: v2.1.107
Model: Sonnet 4.5

Issue Summary

Figma MCP server shows as "Connected" but tools never load into Claude Code sessions, despite correct configuration and successful server connection.

Symptoms

1. claude mcp list shows: figma: npx -y figma-mcp - ✓ Connected
2. ToolSearch for Figma tools returns: "No matching deferred tools found"
3. Figma tools (mcp__figma__get_file, mcp__figma__get_images, etc.) are not available
4. Issue persists after multiple restarts (Ctrl+C, Ctrl+D, full restart)

Configuration

File: ~/.mcp.json

"figma": {
  "command": "npx",
  "args": ["-y", "figma-mcp"],
  "env": {
    "FIGMA_ACCESS_TOKEN": "figd__***"
  }
}

Settings: ~/.claude/settings.json

• enableAllProjectMcpServers: true
• No enabledMcpjsonServers (was removed as deprecated)

Diagnostics Performed

1. Server Connection

$ claude mcp list
figma: npx -y figma-mcp - ✓ Connected

2. Direct Package Test

$ echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | npx -y figma-mcp

Result: Package correctly exposes 5 tools:

• get_file
• get_images
• get_comments
• list_files
• get_component

3. MCP Server Details

$ claude mcp get figma
figma:
  Scope: Project config (shared via .mcp.json)
  Status: ✓ Connected

4. Package Versions

• figma-mcp: v0.1.4 (correct package, verified via npm)

Comparison: Working vs Non-Working

✅ Confluence MCP (WORKS)

• Same configuration structure in .mcp.json
• Shows "Connected" in claude mcp list
• Tools ARE available (mcp__confluence__*)

❌ Figma MCP (FAILS)

• Same configuration structure in .mcp.json
• Shows "Connected" in claude mcp list
• Tools NOT available (mcp__figma__*)

Expected Behavior

After MCP server connects, tools should be available in Claude Code sessions via ToolSearch and direct invocation.

Actual Behavior

MCP server connects successfully, but tools never load into the session. No error messages are shown.

Attempted Fixes

1. ✅ Verified correct package name (figma-mcp not figma-mcp-server)
2. ✅ Removed deprecated enabledMcpjsonServers from settings.json
3. ✅ Multiple full restarts (>5 attempts)
4. ✅ Verified token format is correct
5. ✅ Confirmed package works when tested directly

Impact

Unable to use Figma MCP integration despite correct configuration. Requires manual workaround using Figma API directly via curl/bash.

Workaround

Using Figma REST API directly:

curl -H "X-Figma-Token: $FIGMA_ACCESS_TOKEN" \
  "https://api.figma.com/v1/files/{file_key}"

Suggested Fix: Investigate why figma-mcp package tools don't register with Claude Code despite successful connection, when other MCP servers (Confluence) work correctly with identical configuration patterns.

What Should Happen?

Expected Behavior

After MCP server connects, tools should be available in Claude Code sessions via ToolSearch and direct invocation.

Error Messages/Logs

Steps to Reproduce

Asking Claude to verify Figma

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

v2.1.107

Platform

AWS Bedrock

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response