Make MCP Server `name` and `title` configurable

[Anika-Sol]

Describe the feature or problem you’d like to solve

In our organization we would like to use the GitHub MCP Servers to connect to our GitHub Enterprise Server instances as well as to github.com.
For this use case we start multiple MCP server instances (stdio and http) which works fine in general.

From time to time though, the agents get confused between the running MCP servers, because all of the GitHub MCP servers identify with the same name and title in the serverInfo field of the Initialization Response.
This leads to problems in the communication between the agent and the correct GitHub MCP Server.

Proposed solution

It would help if the server name and title could be configured during the start of the server. Both an environment variable as well as a flag for the local server would be beneficial. PR #2160 would solve our issue.

Additional context

Current response structure of the Initialization Response:

{
    "jsonrpc": "2.0",
    "id": "test",
    "result": {
        "capabilities": {
            "completions": {},
            "prompts": {},
            "resources": {},
            "tools": {}
        },
        "protocolVersion": "2024-11-05",
        "serverInfo": {
            "name": "github-mcp-server",
            "title": "GitHub MCP Server",
            "version": "v0.31.0",
            "icons": [
                ...
            ]
        }
    }
}

The fields reult.serverInfo.name and result.serverInfo.title are constant and currently hard coded here.