Skip to content

update modelcontextprotocol sdk to version 1.25.3#504

Open
manikanta5827 wants to merge 3 commits intostrands-agents:mainfrom
manikanta5827:manikanta-upgrade_mcp_sdk
Open

update modelcontextprotocol sdk to version 1.25.3#504
manikanta5827 wants to merge 3 commits intostrands-agents:mainfrom
manikanta5827:manikanta-upgrade_mcp_sdk

Conversation

@manikanta5827
Copy link

Description

Update MCP SDK to v1.25.3 and fix test transport

Description:

  • This PR updates the modelcontextprotocol SDK dependency and addresses a configuration issue in the test transport layer.

Changes:

  • Chore: Bumped modelcontextprotocol SDK version to 1.25.3.
  • Fix: Added the required sessionIdGenerator to streamableHTTPServerTransport to fix test execution.

Related Issues

#453

Documentation PR

N/A

Type of Change

Bug fix

Testing

How have you tested the change?

  • I ran npm run check

Checklist

  • I have read the CONTRIBUTING document
  • I have added any necessary tests that prove my fix is effective or my feature works
  • I have updated the documentation accordingly
  • I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

// Create a new transport for each request (stateless mode)
const transport = new StreamableHTTPServerTransport({
enableJsonResponse: true,
sessionIdGenerator: () => 'test-session',
Copy link
Member

Choose a reason for hiding this comment

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

Can you elaborate a bit more on this change? It looks like it is still considered optional in 1.25.3 (definition, alias).

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