How do I install the Qmcp Sync skill?

Run npx skillmds@latest add tomevault-io/qmcp-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Qmcp Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Qmcp Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Qmcp Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Qmcp Sync?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Qmcp Sync by tomevault-io — Agent Skill

Name: Qmcp Sync
Author: tomevault-io

File contents

Qmcp-sync

Role

Manage QE's global MCP registry and synchronize shared server definitions into client-specific config files.

Commands

Initialize the global registry

node scripts/qe_mcp.mjs init-registry

Inspect paths and registry health

node scripts/qe_mcp.mjs doctor

Preview sync

node scripts/qe_mcp.mjs sync --dry-run

Apply sync

node scripts/qe_mcp.mjs sync

Sync one client only

node scripts/qe_mcp.mjs sync --client codex
node scripts/qe_mcp.mjs sync --client gemini
node scripts/qe_mcp.mjs sync --client claude

Registry Behavior

The default registry lives at:

~/.qe/mcp/registry.json

It can contain:

qeFramework MCP server
native MCP servers
remote MCP servers
CLI-wrapped servers such as cli-anything style adapters

Secret Handling

If a server needs credentials:

do not store plaintext tokens in the client config
store them with Qsecret
reference them through envSecrets in the registry

QE will launch the MCP through qe_secret_launch.mjs so the child process receives the env vars without exposing the values in config files.

Expected Behavior

Use this skill when the user wants one MCP configuration source for Claude, Codex, and Gemini.
Prefer the QE registry over editing three client config files by hand.
Explain honestly that client behavior still differs even when the same server is synced to all three.

Will

Keep one MCP registry as the source of truth
Sync shared config to supported clients
Support generic MCP entries, not only QE's own server

Will Not

Claim all clients interpret prompts or tools identically
Store plaintext secrets in the synced config files

Source: inho-team/qe-framework — distributed by TomeVault.

---name: qmcp-syncdescription: Manage QE Framework global MCP registry and sync shared MCP server definitions to Claude, Codex, and Gemini configs. Use when the user wants one MCP source of truth across clients. Use when this capability is needed.---# Qmcp-sync## RoleManage QE's global MCP registry and synchronize shared server definitions into client-specific config files.## Commands### Initialize the global registry```bashnode scripts/qe_mcp.mjs init-registry```### Inspect paths and registry health```bashnode scripts/qe_mcp.mjs doctor```### Preview sync```bashnode scripts/qe_mcp.mjs sync --dry-run```### Apply sync```bashnode scripts/qe_mcp.mjs sync```### Sync one client only```bashnode scripts/qe_mcp.mjs sync --client codexnode scripts/qe_mcp.mjs sync --client gemininode scripts/qe_mcp.mjs sync --client claude```## Registry BehaviorThe default registry lives at:```text~/.qe/mcp/registry.json```It can contain:- `qeFramework` MCP server- native MCP servers- remote MCP servers- CLI-wrapped servers such as `cli-anything` style adapters## Secret HandlingIf a server needs credentials:- do not store plaintext tokens in the client config- store them with `Qsecret`- reference them through `envSecrets` 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.## Expected Behavior- Use this skill when the user wants one MCP configuration source for Claude, Codex, and Gemini.- Prefer the QE registry over editing three client config files by hand.- Explain honestly that client behavior still differs even when the same server is synced to all three.## Will- Keep one MCP registry as the source of truth- Sync shared config to supported clients- Support generic MCP entries, not only QE's own server## Will Not- Claim all clients interpret prompts or tools identically- Store plaintext secrets in the synced config files---> Source: [inho-team/qe-framework](https://github.com/inho-team/qe-framework) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Qmcp Sync