Objects deleted unexpectedly when Figma Developer MCP server is connected via Claude Code

Summary Design objects (components, layers) in a Figma file were silently deleted at unknown points while the Figma Developer MCP server (figma-developer-mcp) was active. Unexpected version auto-saves were also recorded at times when no intentional edits were made.

Environment

• Figma Developer MCP: figma-developer-mcp v0.8.1 (--stdio transport)
• MCP client: Claude Code v2.1.91 (Anthropic)
• OS: Windows 11 Pro
• Figma access: via Personal Access Token (API key)

Observed behavior

1. Multiple design objects disappeared from a delivery file without any intentional edit.
2. Version history showed auto-saves at unexpected timestamps (e.g., 18:06 and 08:06) that did not correspond to any deliberate user action.
3. The issue affected multiple screens, not limited to a single component.

Likely trigger The MCP server process starts automatically when Claude Code opens the associated project, even when no Figma tools are explicitly called in the session. It is unclear whether the deletions occur at server initialization, during idle polling, or during tool invocations.

Reproducibility Not reproducible on demand. Discovered after the fact via version history.

Workaround applied Removed the MCP server configuration from the Claude Code project settings to prevent the process from starting automatically. Will use a separate copy of the delivery file for any future MCP access.

Request

• Clarification on whether figma-developer-mcp makes any write/mutating API calls during initialization or idle state.
• A read-only mode option to prevent accidental mutations.
• Better audit logging in version history to identify which API client triggered a save.