Synchronize MCP server configurations across 20+ AI agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-synchro","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-synchro One config file. Every AI agent. Synced. Keep your MCP (Model Context Protocol) server list in a single master file and push it to Claude Desktop, Cursor, Codex CLI, Gemini CLI, VS Code, Windsurf, Cline, Roo, and 15+ more — all at once. ## The problem MCP servers are tools that AI agents can call: a filesystem browser, a web search tool, a database connector, a code executor. Every agent you use has its own config file in its own format, in its own folder, on its own path. Add a new MCP server manually and you are editing a dozen files. Rename one and you are hunting through JSON and TOML spread across `~/Library/`, `~/.config/`, and `%APPDATA%`. One agent uses `mcpServers`, another uses `mcp_servers`. One wants JSON, one wants TOML with snake_case keys. ## The solution `mcp-synchro` maintains a single **Source of Truth** file (`mcp.json`). You edit that one file. Then: ```bash mcp-synchro push # stamp your MCP servers into every agent config on this machine mcp-synchro pull_new # grab any servers an agent has that your master file doesn't mcp-synchro pull_all # rebuild the master file from scratch using every agent's current config ``` The tool reads each agent's native config format, updates only the MCP servers section, and leaves everything else (API keys, UI preferences, keybindings) untouched. ## May 2026 Ecosystem & Antigravity Support `mcp-synchro` fully supports Google's **Antigravity 2.0 Ecosystem** introduced at Google I/O 2026, alongside deprecation and migration utilities for the legacy Gemini CLI. ### The Antigravity Split Google has transitioned its developer interfaces into three distinct products, each with its own configuration path: - **Antigravity Desktop 2.0**: Standalone agent desktop (`~/.gemini/antigravity/mcp_config.json`) - **Antigravity IDE**: Developer workspace editor (`~/.gemini/antigravity-ide/mcp_config.json`) - **Antigravity CLI (`agy`)**: High-performance terminal coding agent (`~/.gemini/anti…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.