modelcontextprotocol
What does the proxy do?
I don't understand the purpose of the proxy. I thought maybe it would allow me to man-in-the-middle between my client and server and snoop on traffic, but I've tried SSE and Streamable and it doesn't seem to work that way.
Is this just a naming thing and proxy means something different than I expect, or am I missing something?
The 'proxy' is really just the server-side component of the Inspector app, which takes care of doing things that you can't or wouldn't want to do in the browser. Its the part of Inspector that actually connects to a MCP Server.
When you say 'snoop on traffic' do you mean that you want to debug the communication between the Inspector as the MCP Client and an MCP Server, or do you mean something else, like using this as a middleman between another client app and a server?
There's a couple different meanings to 'client' in the app, so not sure it would be less confusing to call it that, but I did add a blurb in the README to explain more about what the components are doing in relation to each other: https://github.com/modelcontextprotocol/inspector?tab=readme-ov-file#architecture-overview
I'll close this issue but feel free to re-open if there's more clarity you think we should provide in the documentation.