Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Provider-neutral entry point for discovering, planning and synchronizing MCP configuration between user-selected providers and app classes. The user selects truth, targets and scope; no provider is an implicit hub.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | -41% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -48% | 0% |
| case-04 | ✗→✓ | ▲ Improved | -45% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -28% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -35% | 0% |
<img src="banner.png" width="100%" alt="mcp-config-sync banner">
> Deutsch — Offizielle Deutsch-Version / Documento Oficial en Deutsch.
This is the MCP-focused entry point to agent-config-sync. It assumes no provider, app or master file.
across app classes, within one app class across providers, an explicit list, or every detected provider and class.
agent-config-sync/scripts/sync.py --discover, then --offer.registry.json, review --plan, and only then use--apply --yes.
Discovery and offers are read-only. There is no implicit hub and no implicit “sync all”. The former Claude Code↔Claude Desktop scripts are a legacy profile, not the generic default.
Other measured skills in the registry, with their headline benchmark lift.