skills.rest
inho-team
inho-teamOFFICIAL
Explore all skills by this author →
GitHub

Qmcp-sync

Sync MCP registry definitions across Claude, Codex, and Gemini configurations.

6|Updated Mar 14, 2026
Search Tags:#synchronization#mcp#cloud#registry#secret-management#client-config#qe-framework
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill qmcp-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Qmcp-sync
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qmcp-sync
Command: npx skills add https://github.com/inho-team/qe-framework --skill qmcp-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Centralize and synchronize QE's MCP configuration across Claude, Codex, Gemini to ensure consistent behavior and reduce manual edits.

Core Features & Use Cases

  • Initialize a shared global MCP registry and apply updates to all clients.
  • Sync definitions to client configs (Claude, Codex, Gemini) with dry-run and full-sync options.
  • Securely manage credentials using environment secrets without storing plaintext in configs.

Quick Start

Run a dry-run of the MCP sync to preview changes, then perform the full sync to update Claude, Codex, and Gemini configurations.

Frequently Asked Questions about Qmcp-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize MCP configurations across Claude, Codex, and Gemini clients?▼

You can synchronize MCP configurations across multiple clients by applying updates from a centralized registry at ~/.qe/mcp/registry.json to each platform's config file, ensuring a single source of truth without manual edits.

What is a central MCP registry and how does it keep client configs consistent?▼

A central MCP registry is a shared JSON file that stores all your Model Context Protocol definitions. It keeps client configs consistent by serving as a single source of truth that pushes updates to Claude, Codex, and Gemini automatically.

How do I preview MCP sync changes before applying them to client config files?▼

You can preview changes by running a dry-run of the MCP sync. This simulates the update process and shows exactly what modifications will be made to Claude, Codex, and Gemini configurations before committing them.

Can I sync MCP definitions to only one specific client instead of all platforms?▼

Yes, the MCP sync supports per-client sync options. You can target individual platforms like Claude, Codex, or Gemini specifically, rather than pushing the full registry updates to all client configurations at once.

How do I manage credentials and secrets in MCP configs without storing plaintext?▼

You can securely manage credentials by using encrypted secrets via Qsecret and referencing environment secrets. This prevents storing plaintext credentials directly in your Claude, Codex, or Gemini configuration files.

Why do my MCP definitions keep diverging across different AI coding clients?▼

MCP definitions diverge because each platform uses separate client config files. Using a central registry sync applies a single source of truth across Claude, Codex, and Gemini to eliminate this drift.

Related Skills

Explore More Software Engineering Skills→
JDL440JDL440

Agent Tool-Calling Architecture Pattern

Define a centralized tool registry for agent tool-calling with per-agent allowlists.

Community
Advanced
tecnologia-ibtechtecnologia-ibtech

geo-repo-sync

Synchronize geo-claude changes into geo-codex with dry-run previews and conflict detection.

Community
Intermediate
nateberkopecnateberkopec
111

env-to-fnox

Migrates plaintext .env secrets to fnox-backed management using 1Password and mise.

Community
Advanced
CUexterCUexter
2

nano-pdf

Edit PDF text on specific pages via natural-language prompts.

Community
Intermediate