[Suggestion] Have the MCP Config file follow current MCP Server config file conventions

[bennettaur]

I think it would be easier for adoption if the config file this uses looks more like the config from other tools like Claude and Cursor, allowing you to easily copy and past current configs to try it out

From your example

{
  "servers": [
    {
      "name": "Server 1",
      "transport": {
        "command": "/path/to/server1/build/index.js"
      }
    },
    {
      "name": "Server 2",
      "transport": {
        "command": "server2-command",
        "args": ["--option1", "value1"],
        "env": ["SECRET_API_KEY"]
      }
    },
    {
      "name": "Example Server 3",
      "transport": {
        "type": "sse",
        "url": "http://localhost:8080/sse"
      }
    }
  ]
}

Could just be

{
  "mcpServers": {
    "server1": {
      "command": "/path/to/server1/build/index.js"
    },
    "server2": {
        "command": "server2-command",
        "args": ["--option1", "value1"],
        "env": ["SECRET_API_KEY"]
    },
    "server3": {
        "url": "http://localhost:8080/sse"
    }
  }
}

I can try to put up a PR if you like this idea