Summary

This PR adds an optional description field to the Implementation interface to align with the MCP registry's server.json format and provide human-readable context during the initialization handshake.

Changes

1. Schema Update: Added optional description field to Implementation interface in schema/draft/schema.ts
2. Changelog: Added entry to minor changes section in docs/specification/draft/changelog.mdx

Motivation

The MCP registry's server.json format includes a description field alongside name, title, version, websiteUrl, and icons. Adding this field to the Implementation interface:

• Aligns protocol with registry format: Servers can now expose the same description during initialization that they publish to the registry
• Provides richer context: Both clients and servers can describe their purpose and capabilities during the handshake
• Complements existing fields: Works alongside the existing instructions field in InitializeResult, where description provides a brief summary and instructions provides detailed usage guidance

Example Usage

Server example:

{
  name: "weather-server",
  title: "Weather Data Server", 
  description: "Provides real-time weather data and forecasts for global locations",
  version: "1.0.0"
}

Client example:

{
  name: "claude-desktop",
  title: "Claude Desktop",
  description: "Desktop application for interacting with Claude AI and MCP servers",
  version: "0.5.0"
}

Registry Alignment

The MCP registry server.json structure includes:

• name (required) - unique identifier
• title (optional) - display name
• description (required in registry) - brief explanation
• version (required) - semantic version
• websiteUrl (optional) - project homepage
• icons (optional) - icon array

Our Implementation interface now supports all of these fields through BaseMetadata, Icons, and the newly added description field.

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com