Skip to content

Conversation

@matiasedgeandnode
Copy link

@matiasedgeandnode matiasedgeandnode commented Oct 16, 2025

Motivation and Context

Fixes #774

How Has This Been Tested?

I've added 3 tests.

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

@matiasedgeandnode matiasedgeandnode requested a review from a team as a code owner October 16, 2025 17:08
@KKonstantinov
Copy link
Contributor

Detailed errors are important for production readiness, I'd vote for PRs like this to get priority.

@felixweinberger felixweinberger self-assigned this Oct 21, 2025
@felixweinberger felixweinberger added the needs maintainer action Potentially serious issue - needs proactive fix and maintainer attention label Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs maintainer action Potentially serious issue - needs proactive fix and maintainer attention

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Include McpError 'data' payload in JSON-RPC error response

3 participants