Skip to content

Conversation

@bzsurbhi
Copy link

Added support for long-running operations

Motivation and Context

  • Client → Server - CallToolAsyncRequest
  • Server → Client - CallToolAsyncResult → AsyncOperation
  • Client → Server(Poll) → GetOperationRequest → RequestId
  • Server → Client → GetOperationResult → AsyncOperation(status and resourceUri)
  • Once status is ACTIVE
    • Client → Server - ReadResourceRequest(resourceUri)

xPHDRzim38Rl_XL4pcboD-2YWL4CERGRtFKqx20eZADMbZoASbi4_U-Zh3XT0GCTTjcb5tz8vCl7BobV1LR4iRD5BtUZJQySGsqDEdwtT8Sq81L5LS7M6JQAZNTGLKMEXOlBKqW9xBqDQwsitOGNf-7eL8TBKDJ6JaB34XuH-uqr0xuMEGak93yhbL1BvdVH6BCR3D4o77sFDDOiOLp_Ehs_5eNpZE2Jp8aIuFePTPJLn08g

How Has This Been Tested?

Breaking Changes

Non breaking changes

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

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

Labels

None yet

Projects

No open projects
Status: Draft

Development

Successfully merging this pull request may close these issues.

1 participant