Fix n8n HTTP MCP compatibility by filtering extra parameters before validation #2
+2,254
−1,179
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.
Description
n8n's remote HTTP MCP sends metadata fields (
sessionId,action,chatInput,toolCallId) in tool arguments, causing Pydantic validation to fail with "Unexpected keyword argument" errors.Changes
Core Fix
FunctionTool.runTesting
Example
Type of Change
Complexity
Complexity: Monkey-patches FastMCP's validation layer to filter parameters. Duplicates some core method logic to maintain functionality after filtering.
How Has This Been Tested?
Checklist
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.