Add dev scripts for mitmproxy debugging and fix JSON-RPC error responses #23
+83
−13
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.
Summary
dev-with-mitm.shfor TUI-based traffic inspection using mitmproxydev-with-mitmweb.shfor web UI-based traffic inspection using mitmwebidfield in JSON-RPC error responses (required by JSON-RPC 2.0 spec)zod-to-json-schemato Zod v4's nativez.toJSONSchema()Details
Dev scripts
The mitmproxy scripts help developers debug MCP traffic by running the server through a reverse proxy that intercepts all client requests:
Both scripts:
JSON-RPC fix
The JSON-RPC 2.0 spec requires an
idfield in error responses. Added"id": nullto all error responses inshttp.ts.Zod migration
Replaced
zod-to-json-schemawith Zod v4's built-inz.toJSONSchema()for tool input schema generation.Test plan
idfield🤖 Generated with Claude Code