Description
The MCP spec schema for Implementation, which is used for clientInfo and serverInfo in InitializeRequestParams and InitializeResult, features the two fields
title for a human-readable title of the MCP client/server, and
description for a human-readable description of the MCP client/server.
Curiously, it is not possible to set these basic fields for server and client with the Python SDK.
To be more precise, types.Implementation only supports setting the title (via the superclass BaseMetadata), the description is missing altogether and therefore can't be set for both client and server.
In addition, while the client accepts an Implementation-type client_info object during initialization (so it at least permits setting the title), the server only accepts a server.models.InitializationOptions-type init_options object, which doesn't support neither title nor description.
The feature request is to support setting the title and the description for both clients and servers.
The use case is as the MCP specification says: I'd like to provide human-readable titles and descriptions to MCP hosts.
References
No response
Description
The MCP spec schema for
Implementation, which is used forclientInfoandserverInfoinInitializeRequestParamsandInitializeResult, features the two fieldstitlefor a human-readable title of the MCP client/server, anddescriptionfor a human-readable description of the MCP client/server.Curiously, it is not possible to set these basic fields for server and client with the Python SDK.
To be more precise,
types.Implementationonly supports setting the title (via the superclassBaseMetadata), the description is missing altogether and therefore can't be set for both client and server.In addition, while the client accepts an
Implementation-typeclient_infoobject during initialization (so it at least permits setting the title), the server only accepts aserver.models.InitializationOptions-typeinit_optionsobject, which doesn't support neither title nor description.The feature request is to support setting the title and the description for both clients and servers.
The use case is as the MCP specification says: I'd like to provide human-readable titles and descriptions to MCP hosts.
References
No response