Skip to content

How to setup Claude Desktop to use a server proxied by this inspector? #267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
julien-c opened this issue Apr 4, 2025 · 3 comments
Closed
Labels
question Further information is requested

Comments

@julien-c
Copy link

julien-c commented Apr 4, 2025

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?

@NishealJ
Copy link

NishealJ commented Apr 4, 2025

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 😁.

@olaservo
Copy link
Member

@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.

@olaservo olaservo added the question Further information is requested label Apr 27, 2025
@olaservo
Copy link
Member

Going to close this, but please feel free to re-open if needed.

@olaservo olaservo closed this as not planned Won't fix, can't repro, duplicate, stale Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants