Skip to content

support 405 response from servers that don’t support streaming #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 27, 2025

Conversation

stallent
Copy link
Contributor

Motivation and Context

Some MCP servers do not support streaming from the GET. They should return a 405 to denote that lack of support. Currently the client retries on errors and should not retry if it knows the server does not support it.

How Has This Been Tested?

Stood up a server using the latest TS SDK from Anthropic configured to not support

Breaking Changes

none

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

@mattt
Copy link
Contributor

mattt commented Apr 27, 2025

Thank you, @stallent!

@mattt mattt merged commit ccb070f into modelcontextprotocol:main Apr 27, 2025
4 checks passed
@stallent stallent deleted the 405support branch May 12, 2025 12:52
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.

2 participants