How this command is triggered — by the user, by Claude, or both
Slash command
/slop-mcp:slop-migrateThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Migrate MCP Configurations to slop-mcp Read existing Claude Code MCP server configurations and register them with slop-mcp. ## Steps 1. Read the user's existing MCP configuration. Check these locations: - Claude Desktop: `~/.config/claude/claude_desktop_config.json` (Linux) or `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) - VS Code: `.vscode/mcp.json` - Claude Code settings: `~/.claude/settings.json` - Project `.mcp.json` 2. Parse each `mcpServers` entry to extract name, command, args, and env. 3. Call `manage_mcps` with `action: "list"` to che...
Read existing Claude Code MCP server configurations and register them with slop-mcp.
Read the user's existing MCP configuration. Check these locations:
~/.config/claude/claude_desktop_config.json (Linux) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS).vscode/mcp.json~/.claude/settings.json.mcp.jsonParse each mcpServers entry to extract name, command, args, and env.
Call manage_mcps with action: "list" to check what is already registered.
For each server not already registered, call manage_mcps with action: "register":
mcp__plugin_slop-mcp_slop-mcp__manage_mcps
action: "register"
name: "<server-name>"
type: "command"
command: "<command>"
args: ["<arg1>", "<arg2>"]
env: { "KEY": "value" }
scope: "user"
Ask the user which scope to use:
"user" -- saved to ~/.config/slop-mcp/config.kdl, persists across projects"project" -- saved to .slop-mcp.kdl, persists for this project only"memory" -- runtime only, for testing before committingReport results: which servers were migrated, which were skipped (duplicates), and any errors.
npx claudepluginhub standardbeagle/standardbeagle-tools --plugin slop-mcp/cc-mcpManages MCP servers for Claude Code: add (filesystem, PostgreSQL, GitHub, Slack, Puppeteer, etc.), remove, list status, test connectivity, troubleshoot issues.
/bridge-mcpMirrors every MCP server from .mcp.json (except codex-cli) into .codex/config.toml so Codex CLI can use the same project MCP tools as Claude Code. Idempotent — skips already-configured servers.