Overture — Sincronização de Configurações MCP
jander99/overture
Uma única fonte de verdade para MCP servers em todos os seus IDEs
Ver no GitHubCLI que mantém suas configurações de servidores MCP sincronizadas entre todos os assistentes de codificação instalados (Claude Code, GitHub Copilot, Cursor, Windsurf, Cline, etc). Define seus MCP servers uma vez e o Overture propaga automaticamente para cada plataforma, respeitando seus formatos e esquemas nativos.
Instalação
npx convez-ai jander99/overture1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Sincronizar configurações MCP entre Claude Code, GitHub Copilot e Cursor
- Detectar automaticamente quais plataformas de codificação estão instaladas
- Evitar duplicação manual de configurações MCP em múltiplas ferramentas
- Identificar e relatar conflitos e drift de configuração entre plataformas
Veredito

Overture resolve um problema real para quem usa múltiplos assistentes de IA: manter MCP servers em sync manualmente é trabalhoso e propenso a erros. A CLI está em fase de maturação (primeira versão pronta), com detecção read-only funcional e planos para escrita sincronizada. Essencial para fluxos de trabalho com várias ferramentas.
README
A tradução para o português deste README ainda está na fila.
overture
overture is a CLI utility that keeps your MCP (Model Context Protocol) server
configurations in sync across every installed LLM coding platform on your
machine. Define your MCP servers once, and overture propagates them to the
configuration files of every detected client — Claude Code, OpenCode, VS Code /
GitHub Copilot, Cursor, Windsurf, Cline, Roo Code, Continue, Codex, Zed, Aider,
and friends.
It is the MCP analog of the "npx skills" workflow: just as skills syncs Agent
Skills across coding agents, overture syncs MCP servers.
Install
overture is published to npm as @jander99/overture.
# Run without installing (uses the latest published version):
npx @jander99/overture@latest --help
# Install globally:
npm install -g @jander99/overture
overture detect
Requires Node.js >= 24 (the CLI's first published version targets the Node 24 LTS baseline; local Node 25 also works).
Status: the npm package shape is ready and the first publish is gated behind a manual approval step. See
.omo/plans/npm-npx-readiness-phase-set.mdfor the publish-readiness phase-set.
What it does
- Detects which MCP-capable LLM platforms are installed on the host by probing executables, IDE extensions, and configuration files.
- Reads your canonical MCP server definitions from a single source of truth.
- Writes equivalent entries into each platform's native configuration
location, respecting that platform's schema and transport conventions
(
mcpServers,servers,mcp,context_servers, YAML lists, TOML tables, etc.). - Reports drift, conflicts, and unsupported fields so you can resolve them explicitly instead of silently losing configuration.
See docs/coding-platform-mcp-configurations.md
for the per-platform catalog that drives detection and writing logic.
The detect command
The currently-shipped command is overture detect. It is a read-only
inventory: it never reads, writes, syncs, or modifies any configuration file.
It scans the host and reports which MCP-capable LLM platforms are installed, using two complementary strategies:
- Binary-first (e.g.
claude,opencode,codex,copilot,aider): the platform is reported as installed when its canonical CLI is found on the processPATH. The CLI never spawns subprocesses; executable discovery is a pure filesystem scan that respects POSIX executable bits, WindowsPATHEXT, and WSL-visible.exeentries. - Marker-only (e.g. Cursor, Zed, Cline, Roo Code, Continue, GitHub Copilot VS Code, GitHub Copilot Cloud Agent): the platform is reported as installed when a known config or extension-storage path is present.
For every platform the report includes three orthogonal signals:
installed— the platform app/CLI is on this machine.mcpConfigured— the user has populated the expected MCP section in the platform's config file (parser-backed for JSON, JSONC, and TOML formats).mcpSupport— whether the platform has a known MCP client surface (supported,unsupported, orunknown).
Additional surface area:
- Stale config is reported via
orphanedMcpLocations: an MCP config file is present for a platform that is not currently installed (e.g. a leftover~/.codeium/windsurf/mcp_config.jsonfrom a previous Windsurf install). Stale config alone never implies install. - Unsupported tools (e.g. Aider has a CLI but no first-party MCP client
surface in v1) are surfaced as installed inventory entries with
mcpSupport: unsupportedandmcpConfigured: false, so you can see them without being misled into expecting MCP sync to work.
Usage
# Print installed platforms, configured/unsupported/orphaned sections
overture detect
# Machine-readable: full 14-platform inventory with all additive fields
overture detect --json
# Print usage and exit 0
overture detect --help
overture --help
overture help
The human-readable output has three sections that appear only when relevant: "Detected MCP-capable platforms", "Installed tools without MCP support (inventory)", and "Orphaned MCP configurations (no platform installed)". No ANSI color is emitted; the output is plain text suitable for piping.
The JSON output is the full inventory: all 14 platform entries, including
those not installed, with flat additive fields (detectionStrategy,
mcpSupport, executableNames, matchedExecutables, mcpConfigured,
matchedMcpLocations, orphanedMcpLocations, reasonCode).
detect will not write to or modify any of the files it inspects, and it makes no writes anywhere.
Repository layout
overture/
├── apps/
│ └── cli/ # The `@jander99/overture` CLI (entry point: src/main.ts)
├── docs/
│ └── coding-platform-mcp-configurations.md
├── nx.json # NX workspace configuration
└── package.json # Yarn 4 workspaces root
The workspace is a Yarn 4 monorepo orchestrated by NX 22. Today only apps/cli
exists; additional apps and shared packages will land under packages/.
Build & execute
The CLI lives in apps/cli. It is built with the @nx/esbuild executor and
shipped as a CommonJS Node bundle.
Run in dev (one-shot)
yarn nx serve @jander99/overture
This builds the project and runs the output through Node.
Build only
yarn nx build @jander99/overture
# Output: apps/cli/dist/main.js
Test
yarn nx test @jander99/overture
Make overture runnable as npx @jander99/overture locally
The CLI exposes a bin entry so you can run it via
npx @jander99/overture (or overture after npm link) from anywhere on
your machine without waiting for the first publish. The workflow is:
# 1. Build and create a global symlink
yarn nx run @jander99/overture:link
# 2. Run it
npx @jander99/overture
# or simply
overture
# 3. When you're done, remove the global symlink
yarn nx run @jander99/overture:unlink
The link script in apps/cli/package.json wraps both steps:
{
"scripts": {
"link": "yarn nx build @jander99/overture --skip-nx-cache && npm link",
"unlink": "npm unlink -g @jander99/overture"
}
}
After editing apps/cli/src/main.ts, rebuild and re-link:
yarn nx run @jander99/overture:link
Build configuration notes
apps/cli/package.json builds with bundle: true and thirdParty: true so
esbuild inlines jsonc-parser into the bundle. smol-toml is loaded at
runtime via createRequire and is declared as a dependency so npm install
sets up the lookup path for npm consumers. The shebang defined in
src/main.ts is preserved by esbuild's bundle: true option. The compiled
dist/main.js is what npm link (and npx) register as the overture
command.
Requirements
- Node.js >= 24 (the CLI targets the Node 24 LTS baseline; matches
@types/nodeafter CI is bumped off Node 20) - Yarn 4 (this repo uses Corepack via
.yarnrc.yml) - A POSIX shell for the
npm linkworkflow
License
MIT — see LICENSE.