[BUG] Figma MCP connector stuck in broken state — can't authenticate or uninstall ("Invalid server ID format")

Preflight Checklist

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

What's Wrong?

Summary

The Figma MCP cloud connector (mcp.figma.com) gets into a corrupted state where it cannot authenticate (shows "Configure" instead of "Connected") and cannot be uninstalled (throws an invalid server ID error). This blocks cloud-based Figma MCP usage entirely, including in Cowork sessions.

Environment

• Claude Code (CLI) on macOS
• Claude desktop app (Mac)
• Figma plugin version: 1.1.0 (from claude-plugins-official)
• Also affects Cowork (sandboxed VM) sessions

Steps to reproduce

1. Have the Figma plugin enabled in Claude Code (figma@claude-plugins-official)
2. In the Claude desktop app, observe that the Figma connector appears under Connectors with the label "Configure" (not the blue "Connected" badge)
3. Clicking "Configure" does not present an OAuth flow — it routes to the desktop extension setup page instead
4. The connector shows "dev local" next to the Figma name, suggesting the install path conflated the cloud connector with the desktop extension
5. Attempting to uninstall the connector produces two yellow error banners:

• Invalid server ID format. Expected UUID or mcpsrv_* tagged ID.
• Failed to disconnect from server.

1. The connector entry remains visible and cannot be removed

Additional context

The Figma plugin's .mcp.json configures two servers:

{
  "figma": {
    "type": "http",
    "url": "https://mcp.figma.com/mcp"
  },
  "figma-desktop": {
    "type": "http",
    "url": "http://127.0.0.1:3845/mcp"
  }
}

Impact

- -The broken connector can't be removed, leaving a zombie entry in the Connectors list
- -Cloud-based Figma MCP is unusable, which means Cowork sessions (sandboxed VMs with no access to localhost) have no Figma integration at all
- -Users may also experience intermittent failures in local Claude Code sessions if tool calls route to the broken cloud connector before falling back to the working desktop extension

### What Should Happen?

- The Figma cloud connector should present an OAuth flow during setup and show "Connected" when authenticated
- Uninstalling a connector should always succeed regardless of server ID format
- The cloud connector and desktop extension install paths should be clearly separated so one doesn't override the other


### Error Messages/Logs

```shell
Invalid server ID format. Expected UUID or mcpsrv_*tagged ID.
Failed to disconnect from server.

Steps to Reproduce

1. Have the Figma plugin enabled in Claude Code (figma@claude-plugins-official)
2. In the Claude desktop app, observe that the Figma connector appears under Connectors with the label "Configure" (not the blue "Connected" badge)
3. Clicking "Configure" does not present an OAuth flow — it routes to the desktop extension setup page instead
4. The connector shows "dev local" next to the Figma name, suggesting the install path conflated the cloud connector with the desktop extension
5. Attempting to uninstall the connector produces two yellow error banners:

• Invalid server ID format. Expected UUID or mcpsrv_* tagged ID.
• Failed to disconnect from server.

1. The connector entry remains visible and cannot be removed

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.42

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

_No response_