You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to this, and I apologize if I missed this info somewhere, but is there way to use the inspector as a proxy between my MCP server and a client like Claude Desktop?
Or does this not make any sense?
The text was updated successfully, but these errors were encountered:
I'm not sure if it can actually act as an interceptor between Claude and the MCP server—Inspector seems to be primarily a debugging tool for MCP servers. While it does run the MCP server on port 6277, it's unclear whether pointing Claude to this URL in the config will allow the traffic to be intercepted.
I'll give it a try, lmk if my understanding is correct.
Actually, I'm also trying to figure out a way to inspect the communication between the MCP client and MCP servers 😁.
@julien-c Since Claude Desktop only speaks in stdio and Inspector is using HTTP for its own proxy to connect to MCP servers, I think you would need a different solution to act as a proxy. If you look at something like mcp-remote its directly proxying from stdio to other transports.
So @NishealJ because of ^^ you would need something else to translate between stdio and a URL if you wanted to intercept communication, but I think its technically possible with one more layer in between.
Hi,
I'm new to this, and I apologize if I missed this info somewhere, but is there way to use the
inspector
as a proxy between my MCP server and a client like Claude Desktop?Or does this not make any sense?
The text was updated successfully, but these errors were encountered: