Skip to content

Conversation

ParanoidUser
Copy link

Ahoy @tzolov! 👋

Motivation and Context

This adds the missing @Deprecated annotation to complete the builder pattern migration started in PR #430.

How Has This Been Tested?

  • Unit Tests: All existing tests are passing

Breaking Changes

No breaking changes. Constructor is still available, but marked deprecated.

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

If the overall goal is to have a single way to create all transport providers via builders, StdioServerTransportProvider might be another candidate that needs some cleanup. I'm open to adding a builder and deprecating constructors if it makes sense.

…onstructor

Complete constructor deprecation from commit 1840f63 addressing potential oversight during initial refactoring

Related to: 1840f63, PR modelcontextprotocol#430
@ParanoidUser ParanoidUser force-pushed the deprecate-remaining-transport-constructor branch from 94a0cbd to 9d3054b Compare August 28, 2025 03:13
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