From qe-framework
Manages a global MCP registry and syncs MCP server definitions across Claude, Codex, and Gemini configs. Keeps one source of truth for MCP configuration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qe-framework:Qmcp-syncThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manage QE's global MCP registry and synchronize shared server definitions into client-specific config files.
Manage QE's global MCP registry and synchronize shared server definitions into client-specific config files.
node scripts/qe_mcp.mjs init-registry
node scripts/qe_mcp.mjs doctor
node scripts/qe_mcp.mjs sync --dry-run
node scripts/qe_mcp.mjs sync
node scripts/qe_mcp.mjs sync --client codex
node scripts/qe_mcp.mjs sync --client gemini
node scripts/qe_mcp.mjs sync --client claude
The default registry lives at:
~/.qe/mcp/registry.json
It can contain:
qeFramework MCP servercli-anything style adaptersIf a server needs credentials:
QsecretenvSecrets in the registryQE will launch the MCP through qe_secret_launch.mjs so the child process receives the env vars without exposing the values in config files.
npx claudepluginhub inho-team/qe-framework --plugin qe-frameworkCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.