Skip to content

Conversation

@Tr1ple-F
Copy link

Added title to McpSchema.Implementation

Motivation and Context

Align the Java SDK with the Python SDK here and the specification of the initialization response in the MCP Specification here.

How Has This Been Tested?

Ran all the tests and tested a basic application to make sure everything still works.

Breaking Changes

Users will have to provide at least null as a parameter to their server/client info. Alternatively one could also make a non-breaking implementation with 2 constructors.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

See Python SDK and Initialize Response in Lifecycle

@Tr1ple-F Tr1ple-F closed this by deleting the head repository Jul 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant