Feature Request: Support for Claude Code Plugins (enabledPlugins)

[vkuprin]

Summary

MyMCP currently manages MCP servers across various clients, including Claude Code (~/.claude.json). However, Claude Code also has a separate plugin system configured via ~/.claude/settings.json under the enabledPlugins key. It would be great to see support for discovering, enabling/disabling, and managing these plugins as well.

What are Claude Code Plugins?

Claude Code plugins are extensions that add tools, skills, and capabilities to Claude Code (Anthropic's CLI agent). They are distinct from MCP servers — plugins are managed through ~/.claude/settings.json rather than ~/.claude.json.

Example configuration:

{
  "enabledPlugins": {
    "context7@claude-plugins-official": true,
    "playwright@claude-plugins-official": true,
    "serena@claude-plugins-official": true,
    "typescript-lsp@claude-plugins-official": false,
    "frontend-design@claude-plugins-official": true
  }
}

Plugins come from registries (e.g., claude-plugins-official) and can be toggled on/off with a boolean value.

Proposed Feature

• Browse available Claude Code plugins (similar to how MyMCP browses the MCP server registry)
• Enable/disable plugins via a toggle UI (writes to ~/.claude/settings.json > enabledPlugins)
• Show plugin metadata — description, what tools/skills each plugin provides
• A new entry in the Supported Clients table or a dedicated section for Claude Code plugins

Config Details

Item	Location
Config file	~/.claude/settings.json
Key	enabledPlugins
Format	"pluginName@registry": true/false

Why This Would Be Valuable

Currently, managing Claude Code plugins requires either:

1. Using claude /plugin commands in the CLI
2. Manually editing ~/.claude/settings.json

Having plugin management in MyMCP would provide a unified GUI for managing both MCP servers and Claude Code plugins — making it a true one-stop shop for AI tool configuration on macOS.