fix: migrate custom request parameters to _meta structure for SDK compatibility #379
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…patibility - Move mcpSessionId, apifyToken, and userRentedActorIds into params._meta object - Newer MCP SDK versions filter out unknown top-level parameters, so _meta is used as standard container - Add ApifyRequestParams type definition for proper typing of _meta structure - Update parameter extraction in tool handlers and task handlers to read from _meta - Refactor parameter injection to use nullish coalescing assignment (??=) for clarity - Allow _meta underscore in ESLint config as standard MCP protocol field - Remove unnecessary parameter deletion after extraction since they're now in _meta - Enable MCP Session ID error throwing since injection is now guaranteed FIXES: Parameters being stripped by newer MCP SDK versions causing task store errors
commit: |
jirispilka
approved these changes
Jan 5, 2026
Collaborator
jirispilka
left a comment
jirispilka
left a comment
There was a problem hiding this comment.
Interesting, I wouldn't expect that a newer version of MCP would stip the extra params. I hope this is going to work 🤞🏻
Thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This solves the issue with missing session id when the stdio server is executed through
npx. Instead of putting the custom props into theparamsin request we use the_metafields. The issue seems that for some reason the npx uses a newer version of SDK that seems to strip the request for custom params, I was able to replicate the error but could not really confirm the root cause.