When parsing environment variables or headers, if a value is explicitly set to null in the JSON config, converting it to the string "None" via str(v) can lead to unexpected behavior (e.g., the subprocess receiving the literal string "None" as an environment variable or header value, which is truthy).

It is safer to defensively filter out keys with None values.

If the configuration uses the VS Code alias "servers" instead of "mcpServers", but the value is not a dictionary, the error message still hardcodes 'mcpServers'.

Dynamically referencing the key that was actually matched in the config provides clearer and more accurate error feedback to the user.

In standard HTML rendering, newlines (\n) in text content are collapsed into a single space unless the element has white-space: pre-line or similar styling. This causes the sliced error messages to run together on a single line, making them difficult to read.

Wrapping the description in a div with the Tailwind class whitespace-pre-line ensures that each error is rendered on its own line.

      if (result.errors.length) {
        toast.warning(summary, {
          description: (
            <div className="whitespace-pre-line">
              {result.errors.slice(0, 5).join("\n")}
            </div>
          ),
        });
      } else {

Preserve Windows args containing quotes during import

When importing a Windows stdio config whose args contain literal quotes (for example a JSON CLI option like {"foo":"bar"}), subprocess.list2cmdline() emits backslash-escaped quotes, but the stored string is later split by parse_stdio_command() using shlex.split(..., posix=False), which does not unescape those sequences. The MCP server process then receives '{\\"foo\\":\\"bar\\"}' instead of the original JSON argument, so these imported servers can fail even though the config is valid; either the joiner needs to match the existing parser, or the parser needs to understand Windows command-line escaping.

Useful? React with 👍 / 👎.