Feature Request: Auto-discover and import extensions from Claude Desktop

Summary

The claude mcp add-from-claude-desktop command currently does not detect or import extensions (.dxt files) that are installed in Claude Desktop. This creates an inconsistent experience where users must manually reconfigure their extensions in Claude Code despite already having them set up in the desktop application.

Current Behavior

• Extensions installed in Claude Desktop are not discovered by claude mcp add-from-claude-desktop
• Only MCP servers from Claude Desktop configuration are imported
• Users must manually reinstall and configure extensions for Claude Code

Requested Behavior

• claude mcp add-from-claude-desktop should detect and import both MCP servers AND extensions from Claude Desktop
• Extensions should be automatically configured and made available in Claude Code
• Maintain compatibility with existing MCP server import functionality

Use Case

As a user who has already configured extensions in Claude Desktop, I want to use the same extensions in Claude Code without having to manually reinstall and reconfigure them. This would provide a seamless experience across both Anthropic tools and reduce setup friction.

Technical Notes

• Extensions are typically stored as .dxt files in the Claude Desktop configuration
• The command should scan the same configuration directory/registry used by Claude Desktop
• Consider handling version compatibility between desktop and CLI environments

Priority

This seems like a straightforward enhancement that would significantly improve user experience and reduce configuration overhead when switching between Claude Desktop and Claude Code.

Additional Context

This feature would make the workflow more consistent and reduce the barrier to adoption for users who want to leverage their existing extension setup in the command-line environment.