Claude Code / AI Coding Tools

Figma MCP server never transitions from auth mode to operational mode #61265

Fix Figma MCP OAuth flow completing but MCP server disconnecting and reconnecting with only auth placeholder tools instead of full Figma toolset Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 21, 2026 1 source Needs local verification

Category: AI Coding Tools
Error signature: Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 21, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Claude Code, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments is a Claude Code failure pattern reported for developers trying to fix figma mcp oauth flow completing but mcp server disconnecting and reconnecting with only auth placeholder tools instead of full figma toolset. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #61265 in anthropics/claude-code by DaveLaFontaine, opened May 22, 2026. Detailed reproduction shows OAuth completes in browser → Claude Code disconnects MCP server → server reconnects with only mcp__figma__authenticate tools. ~/.claude/mcp-needs-auth-cache.json confirms token cached but never persisted to macOS Keychain or Claude Code credentials. Only ~15 min old, highly active. Duplicate check: no matching error in covered-errors.md. Category: AI Coding Tools.

Common causes

GitHub Issue #61265 in anthropics/claude-code by DaveLaFontaine, opened May 22, 2026. Detailed reproduction shows OAuth completes in browser → Claude Code disconnects MCP server → server reconnects with only mcp__figma__authenticate tools. ~/.claude/mcp-needs-auth-cache.json confirms token cached but never persisted to macOS Keychain or Claude Code credentials. Only ~15 min old, highly active. Duplicate check: no matching error in covered-errors.md. Category: AI Coding Tools.

Quick fixes

Confirm the exact error signature matches Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments.
Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments exactly before applying the quick fix.
Compare the failing environment with Claude Code versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments mean in Claude Code?

Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments indicates the workflow described by "Figma MCP server never transitions from auth mode to operational mode #61265" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments?

Check whether this cause matches your environment: GitHub Issue #61265 in anthropics/claude-code by DaveLaFontaine, opened May 22, 2026. Detailed reproduction shows OAuth completes in browser → Claude Code disconnects MCP server → server reconnects with only mcp__figma__authenticate tools. ~/.claude/mcp-needs-auth-cache.json confirms token cached but never persisted to macOS Keychain or Claude Code credentials. Only ~15 min old, highly active. Duplicate check: no matching error in covered-errors.md. Category: AI Coding Tools.

Is the Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments guidance source-backed?

The "Figma MCP server never transitions from auth mode to operational mode #61265" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments?

For "Figma MCP server never transitions from auth mode to operational mode #61265", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Figma MCP gets stuck in authenticate-only tools after successful OAuth, never exposing real tools like get_file or get_comments?

For "Figma MCP server never transitions from auth mode to operational mode #61265", collect the failing Claude Code command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.