Skip to content

Conversation

@aaronpowell
Copy link
Contributor

Motivation and Context

This aligns more with the type structure see in the other SDK's (eg: https://github.com/modelcontextprotocol/python-sdk/blob/main/src/mcp/types.py#L41) while also ensuring they are exposing the JSONRPCRequest (https://github.com/modelcontextprotocol/specification/blob/main/schema/2024-11-05/schema.json#L771-L806) data.

Storing progressToken as an object as it could be an int or string (per https://github.com/modelcontextprotocol/specification/blob/main/schema/2024-11-05/schema.json#L1268-L1274).

Fixes #67

How Has This Been Tested?

I'm using this to implement the "everything server" (not in this branch).

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

@aaronpowell
Copy link
Contributor Author

@stephentoub I think this is the last real blocker to implementing an everything server

@stephentoub stephentoub merged commit 6fa1443 into modelcontextprotocol:main Mar 26, 2025
8 checks passed
@aaronpowell aaronpowell deleted the expose-meta-on-params branch March 26, 2025 03:41
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.

Unable to access progress token in McpTool

2 participants