← ClaudeAtlas

claude-plugin-mcp-managerlisted

Claude Code plugins and MCP servers are managed across marketplaces, validation, token cost, install/update/remove/prune, session-only sources, MCP approvals, strict config, transports, headers, OAuth, and lifecycle failures.
Xopoko/plug-n-skills · ★ 11 · AI & Automation · score 77
Install: claude install-skill Xopoko/plug-n-skills
# Claude Plugin And MCP Manager Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once: the host's plugin-root variable when defined (Claude Code: `PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"`), otherwise this plugin's absolute root path. Covers plugin marketplaces, installed plugins, token-cost details, validation, release tags, scoped installs, session-only plugin loading, MCP server configuration, project approval state, stdio/http/sse transports, headers, env vars, OAuth, and strict-MCP-config runs. ## Inspect First Check the local command surface: ```bash python3 "$PLUGIN_ROOT/scripts/claude_code_inspector.py" --commands plugin "plugin marketplace" "plugin install" "plugin validate" mcp "mcp add" --json ``` Read current state before mutating it: ```bash claude plugin list claude plugin marketplace list claude mcp list ``` Use `claude plugin details <name>` and `claude mcp get <name>` before changing an existing item. ## Plugin Workflow Validate source: ```bash claude plugin validate /path/to/plugin claude plugin validate /path/to/plugin --strict ``` Inspect installed plugin cost/components: ```bash claude plugin details <plugin> ``` Install from a configured marketplace: ```bash claude plugin install <plugin>@<marketplace> --scope user claude plugin install <plugin> --scope project ``` Load a plugin only for one session: ```bash claude --plugin-dir /path/to/plugin claude --plugin-url https://exampl