Skip to content

Conversation

@wei
Copy link
Contributor

@wei wei commented Sep 7, 2025

Fix toast message when copying server entry for a Streamable HTTP transport URL. Updated README and tests.

Motivation and Context

When copying a server entry for an Streamable HTTP server URL, the toast shows "SSE URL has been copied" which is incorrect.

image

How Has This Been Tested?

Tested locally.

Breaking Changes

No.

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

N/A

Copy link
Member

@olaservo olaservo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested this locally, thank you for catching and fixing these inconsistencies! One minor note is that technically the URL based configs mention 'use this URL' even though its the entire server entry. However this is a wording detail that already existed, so not blocking this.

@olaservo olaservo merged commit 2f2dd4c into modelcontextprotocol:main Sep 10, 2025
5 checks passed
@wei wei deleted the fix-copy-toast branch September 10, 2025 16:21
@wei
Copy link
Contributor Author

wei commented Sep 10, 2025

@olaservo Thanks for merging! Would you like me to create a new PR for that change?

Proposing changing

SSE URL has been copied. Use this URL directly in your MCP Client.

to

SSE JSON config has been copied. Use this config directly in your MCP Client.

Feedback welcome!

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