Cliff Hall

Closing this one. It seems as if your `.well-known/oauth-protected-resource` endpoint needs CORS config to allow all origins. It is a public metadata discovery mechanism.

> From my understanding the whole point of having a proxy is to "circumvent" the CORS policy for development as it is only relevant in browser environment. The original point...

This message is not being generated by the Inspector itself. ### Searching the Inspector project for the words "Processing request" Serendipitously, I just merged [a PR that adds a clear...

> I'm having a similar problem but with langgraph, at the moment I want to list available tools, the process never ends and it cannot go to the other nodes....

> Thanks for the quick response! I figured out that I was trying to pass the MCP client object through the config to the graph, but what I needed was...

> Hi @EladAriel, thanks for your work on this! Although multi server support is something that we've talked about before, right now we're more motivated towards stabilizing existing core features...

> Hi, yes, but I need to know exactly what features are required. Of course, and it is a lot. I'm not certain we'd want a separate server with API...

Could you try this with the latest version of the Inspector AND use the correct endpoint: (/mcp not /http) ```shell npx -y @modelcontextprotocol/inspector@latest --cli https://mcp.paypal.com/mcp --transport http --method tools/list --header...

[This PR](https://github.com/modelcontextprotocol/inspector/pull/839) _should_ fix it. It's been merged and will be in the next release. I can run locally, invoking the same entry point that `npx @modelcontextprotocol/inspector` does:

Hi @nitishagar Can you please include before and after screenshots so we can see what this does?