Skip to content

Consolidate McpClientException/McpServerException into McpException#209

Merged
stephentoub merged 1 commit intomodelcontextprotocol:mainfrom
stephentoub:consolidatemcpexception
Apr 4, 2025
Merged

Consolidate McpClientException/McpServerException into McpException#209
stephentoub merged 1 commit intomodelcontextprotocol:mainfrom
stephentoub:consolidatemcpexception

Conversation

@stephentoub
Copy link
Copy Markdown
Contributor

I also normalized CancellationToken exception docs. I'd started doing so before noticing the exceptions were duplicates of each other and didn't really need to be, but didn't revert the doc improvements.

@halter73
Copy link
Copy Markdown
Contributor

halter73 commented Apr 4, 2025

I'm fine with merging these types, but do you agree that a lot of these should ultimately be changed to InvalidOperationExceptions and IOExceptions instead of McpExceptions?

@stephentoub
Copy link
Copy Markdown
Contributor Author

I'm fine with merging these types, but do you agree that a lot of these should ultimately be changed to InvalidOperationExceptions and IOExceptions instead of McpExceptions?

Yes, I'll merge this and then will look at getting rid of the type entirely.

@stephentoub stephentoub merged commit 8fcdf95 into modelcontextprotocol:main Apr 4, 2025
8 checks passed
@stephentoub stephentoub deleted the consolidatemcpexception branch April 4, 2025 01:11
@jeffhandley jeffhandley added the breaking-change This issue or PR introduces a breaking change label Feb 20, 2026
@jeffhandley
Copy link
Copy Markdown
Contributor

Adding the breaking-change label retroactively during release notes revision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking-change This issue or PR introduces a breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants