Paste an MCP config from any client and get it back in the format Zed actually reads — including the format changes nobody documents.
Config files are for the people who already bought. MCP Showcase gives you one link that shows anyone what your server does, without them configuring anything at all.
From Claude Desktop, Cursor, VS Code, Windsurf or anywhere else. We detect the source format.
Root key, endpoint field, transport type, file format — and whether Zed can reach a hosted server at all or needs a local bridge.
The result is in the file format Zed reads, ready to paste into the right location.
MCP standardises the protocol, not the configuration. Moving a server between two clients means changing up to four things, and every one of them fails silently if you miss it — the file parses, the client starts, and the server is simply absent.
settings.json (Zed: Open Settings), in JSON.context_servers here, but
mcpServers, servers, context_servers or
mcp_servers depending on where you are coming from.url for Zed.
Zed's root key is "context_servers", not "mcpServers", and the naming carries through its UI and docs. Nothing copied from another client's config will be read. Zed also settled on this name before the ecosystem standardised, so older guides may not match what your version expects.
Local stdio servers are mostly portable: the command and its arguments mean the same thing everywhere. What changes is the wrapper — the root key, and for JSON clients the entire file syntax. Headers and environment variables come across as they are, so if your config contains a token, it will be in the output. Everything happens in your browser and nothing is uploaded, but strip it first if you would rather.
Porting a config between clients is work that only ever benefits people who already use your server. It does nothing for the person deciding whether to try it. MCP Showcase gives that person a live playground on the same URL — every tool documented and runnable in a browser, with no file to edit and nothing to restart.