⇄
MCP Config Converter
Paste one MCP config and get the equivalent config for the other four clients at once, with per-server field diffs and the entries that cannot be represented. The source is identified from evidence, and candidates are listed rather than guessed.
Runs in browserAI configConversion
Loading tool…
How to use
- Paste one MCP config and get the equivalent configs for the other four clients at once. Everything runs in your browser; the config never leaves this page.
- The source is identified from evidence, not from whichever client it most resembles: the top-level key servers belongs only to VS Code, serverUrl only to Windsurf, a remote entry carrying type can only be Claude Code, and any remote entry rules out Claude Desktop. When the evidence is thin it lists the candidates and says what is missing, because guessing wrong shows up as a config that silently does nothing on one client — far harder to debug than a stated uncertainty.
- Parsing is shape-driven, not client-driven. That follows from the previous point: while the source is unidentified, the intermediate representation still has to be right, or every converted output inherits the same mistake.
- Fields that cannot be represented are reported rather than silently dropped. Dropping cwd or disabled yields a config that looks converted but behaves differently — the most damaging kind of problem in a cross-client migration.
- Claude Desktop's config file is stdio-only, so remote entries cannot be represented there at all; the tool says so plainly instead of handing you a config that is written but inert.
- Converted configs usually need a field or two filled in before a client accepts them; each target lists which fields to verify. This is a converter, not an installer.