info_outlineFirst select "Server type" to see the corresponding fields (Command/Arguments or URL).

• info_outlineValid JSON Format Examples

  Format 1: Object with "mcpServers" key

  {
    "mcpServers": {
      "my-tool": { "command": "npx", "args": ["pkg", "--arg"] },
      "sse-tool": { "type": "sse", "url": "http://..." }
    }
  }

  Format 2: Direct mapping "name": {config}

  {
    "tool-alpha": { "command": "uvx", "args": ["server-a"] },
    "stream-beta": { "type": "streamable_http", "url": "http://..." }
  }

  Format 3: List of objects with "name" field

  [
    { "name": "gamma", "command": "/bin/gamma", "args": ["--conf"] },
    { "name": "delta", "type": "sse", "url": "https://..." }
  ]

  Format 4: Single object with "name" field (Useful for single server import/export)

  {
    "name": "epsilon",
    "command": "docker",
    "args": ["run", "my-image"],
    "env_vars": {"VAR": "value"},
    "server_type": "stdio",
    "is_enabled": false
  }

  Notes:

  • - Server names must be unique.
  • - `command`/`args`/`env` are used for `stdio`. `url`/`type` for `sse`/`streamable_http`.
  • - `env_vars` in Format 4 maps to `env` in generated config.
  • - Windows commands (`cmd /c ...`) are adapted during analysis.
  • - Extra fields are ignored.