Name and version of MCP server?

[m4recek]

Is there a way to specify the name and version of GraphQL MCP server?

From MCP docs

const server = new McpServer({
  name: "weather",
  version: "1.0.0",
  ....
});

[alocay]

Currently the server info is set so the name is "Apollo MCP Server" and the version of the Apollo MCP Server itself. There is no way to currently configure this. Is this a feature you're requesting?

[m4recek]

Is this a feature you're requesting?
Yes please :)

And can we have a way to add a description for tools as well?

[alocay]

What source are you using for your GQL operations (which become tools)? If it's local operation files or I think operation collections you can add comments which will act as a description override. I believe comments in the schema SDL will also be used as descriptions for the operations but comments directly in the operation itself will take precedence.

For example imagine a section of some schema SDL:

type Query {
    customQuery(""" id description """ id: ID!, """ a flag """ flag: Boolean): OutputType
}
...
"""
the description for the enum
"""
enum RealEnum {
    """
    ENUM_VALUE_1 is a value
    """
    ENUM_VALUE_1
    ...
}

the comments for the variables of customQuery will be provided in the input schema. The same is true for the enum. Now if the comment is within the operation defintion's body itself, these take precedence. Consider this basic example:

# operation description
query QueryName(
    # id comment override
    idArg: ID
) { 
    customQuery(id: $idArg) { id } 
}

this will set the description for this tool in the input schema to "operation description".

The one exception to this is if the operation source is a persisted query (PQ) manifest. Due to limitations here, operation body comments are not retained in PQs so they cannot be used.

[m4recek]

@alocay I had issues with tool descriptions on my side, thanks for the examples, it's working just fine.

[kbychu]

@m4recek I can imagine that updating the name and version can be useful. Can you tell me more about why? What does changing the name/version do for your use case?

[m4recek]

@kbychu Internal names and versioning, we have multiple versions of the code deployed in different environments, it would be cool to have it available on the http api as well. Right now, we are solving this by creating version files next to the MCP deployment.